Scott Hanselman

I'm saving this so I can find it easily later. Chris Sells has a post that describes how to give a Mapped Network Drive "FullTrust." Thanks Chris!

[When loading a Project from a Network Drive (like Z:\, perhaps within a VPC) you may receive:]

The project location is not trusted.
Running the application may result in security exceptions when it
attempts to perform actions which require full trust.

What's happening is that VS is detecting that the project on the network drive is getting Intranet permissions according to the good and true workings of .NET Code Access Security (CAS). However, since I'm just trying to pretend that Z is on my PC (and, in fact, it is), I want it to have FullTrust permissions.

To accomplish this, you need to add a new Code Group with an URL membership permission specifying the folder (in URL form) to which you'd like to grant full trust. You can do with the .NET Framework Configuration tool or you can do it from the command line like so:

c:\>caspol -q -machine -addgroup 1 -url file://z:/* FullTrust -name "Z Drive"

Once this new code group is in place, any new .NET processes you start will give any assemblies on the Z drive full trust.

Since awarding new permissions, full trust or not, to any chunk of code is something that can cause a security hole, be careful.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

About   Newsletter

Hosting By

Folks, help me out by voting for this obvious accessibility issue in VS.NET 2005 (Whidbey) Beta 1:

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

About   Newsletter

Hosting By

Folks keep trying to push metaphors (or similes, like, depending on how you say it) a smidge too far. Steve Maine had some words for Mark Baker. That said:

Patrick and I sat down to talk about this:

• REST:
• I write a letter, a document even, and it has no address on it and doesn't even say "Dear Patrick."
• I tell the Postman, remembering that I'm only able to tell him two things, GET and POST, to take this letter to my friend Patrick.
• POST /patrick.aspx HTTP/1.0
• If the Postman puts the document (not a message, considering that he's the only one who knows where it's going) down on the seat, in order to Store and Foward this message - is it a letter? No, it's a document with no destination.
• REST doesn't cover this. The address is out of band.  It's not on the "envelope" as there IS NO ENVELOPE.  Trying to say that the HTTP Headers are a Poor Man's Envelope succeed only in describing a very poor man.
• SOAP
• I write a letter, a document even, and it has no address on it and doesn't even say "Dear Patrick."
• I put it in an envelope (also, a folded piece of paper, except this one has glue on it in certain places and a licky part) and put ATTN: Patrick (WS-Addressing) on the outside with some wax seals (WS-Security) and a Notary Public Stamp (WS-Trust).
• If the Postman puts the document on his seat, the document (now a bona fide message) could be delivered by a substitute Postman.
• Thus, SOAP adds, gasp, value by simply formalizing addressing, containment, and with WS*.*, security and trust.
• And, it's transport independent. The Postman is free to use a Mule or a Segway.

How anyone can argue about this is beyond Patrick and I.

REST is interesting, and when simplicity is called for, knock yourself out.  But seriously, I can see why some may call them RESTafarians because more often than not "Hay now, Mista Postman, tak dis letta to mwa bwoy Patrix. Eim dwon undastan SOAP." doesn't cut it if you really want your letter to arrive.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

About   Newsletter

Hosting By

IMHO, it’s because converting (both projects and your mind) to VB6 to .NET is hard.

• VB6 existed for one reason and one reason only – to hide the complexities of COM.
• VB6 was the Matrix, while VB.NET is as powerful as C#. Some folks say, well, while I'm here, I'll just move over to a language with "C" in it, and maybe I'll get more money?
• VB.NET aims to hide nothing – and the exposure is scary to many.
• VB.NET looks like VB7 - but it's not.
• VB6 solved the problem of multithreaded Windows Forms by not allowing it. 
• VB.NET’s WinForms and the BeginInvoke, AsyncResult, and InvokeRequired of it all is complex for anyone, especially a VB6 Mort.
• VB6 is used by places like "Podunk County School District" and "Whatever, Kansas Dept. of Forestry."  These are places where Microsoft Access is fine, therefore VB6 is "fine."
• Until Microsoft explains why VB6 isn’t "just fine" – folks will linger.
• The Migration Path is not clear and VERY complex – if you did anything funky with OCXs, or if a component vendor didn’t provide you with a migration path, you’re screwed. 
• The Migration Wizard is an amazing chunk of work, but the 20% edge cases are hard.
• Making no decision at all is an implicit decision.  Many VB6 developers are paralyzed. That is a decision not to move forward.
• Safety first, and safety in numbers.

What do you think? Do you have buddies that are still on VB6? What are they doing it about it? Is VB6SP5 "just fine"? Is VB6 a technology that Microsoft should continue to support?

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

About   Newsletter

Hosting By

Absolutely freaking brilliant.  I want to meet this guy.  Crap.  I should have thought of this.

GlucoBoy brings blood sugar monitoring to GameBoy

Guidance Interactive have created GlucoBoy, an attachment for the Nintendo GameBoy that monitors blood sugar levels.  Creator Paul Wessel noticed that his son, who was diagnosed with diabetes at age 3, carried his GameBoy everywhere.  Wessel figured, hey - why not just turn the thing into a blood sugar monitor?  He is also developing games that work with the GlucoBoy beyond the standard testing. [Engadget]

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

About   Newsletter

Hosting By