Article Index

Temporary Projects in Visual Studio 2005

Jeff Key created a great little tool called Snippet Compiler, which allowed you to experiment with some throwaway .NET code. This is useful for doing a quick technical proof of concept (a "spike" in agile practitioner terms). Before Snippet Compiler, I used to fill my Visual Studio Projects folder with a bunch of junk projects that I intended to delete eventually.
However, with Visual Studio 2005, I think Snippet Compiler's days are numbered (no offense Mr. Key). VS2005 supports a seemingly little known feature that I'll call "temporary projects". It allows you to create and work on a new project without saving it to disk. You can work on the project as long as you want. When you close the project, you have the option to save it, but more importantly, you have the option to just discard it (this should all sound familiar to fellow VB6 converts). If you use the new Web Application Project model, you can even use this feature to create throwaway websites.

I use this feature all the time while trying to brush up on on the new functionality in the 2.0 framework.

To enable temporary projects:

1) In Visual Studio 2005, go to the Tools | Options... menu
2) Go to the Projects and Solutions node
3) Uncheck "Save new projects when created"


//off, sry (the ProfileView topic was closed)
"Zoltan -
You've stumbled upon something strange. When I download the release using Firefox, I *also* get the old version. I have checked and re-checked, uploading the new version many times, and I still get the old version. I then tried using IE, and it downloaded the correct new version. I have no idea why at this point, but its something to try.

Sorry, you cannot use it in an admin page to manage other user's profiles. My control is built on Microsoft's Profile Provider framework, and that framework wasn't designed for the use case of manipulating other people's profiles."

I tried to download the new version with IE, and it worked as you said.
really strange. maybe it's someting to do with the caching.

If I want to manage other user's profiles (from admin), I use to use this:
ProfileCommon prof = Profile.GetProfile(UserName);
prof.SetPropertyValue("propertyName", TextBox1.Text);

Why can't ProfileView do the same? Am I misunderstanding something? I'm still new with asp.
Zoltan - March 28, 2006 01:46pm