Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...
- From: Gerry Hickman <gerry666uk@xxxxxxxxxxxxxxxx>
- Date: Sun, 03 Sep 2006 23:26:18 +0100
Hi Owen,
Just to be clear: we are not logging in to our systems with network admin rights, just local admin rights.
Local Admin rights are very bad! Microsoft's whole o/s is a risk when you log on locally with Admin rights because their browser is part of the o/s and has an ActiveX instantiation layer. Browsing to ANY internet site while logged in with local Admin rights puts you machine at HIGH RISK of being infected by trojans and SpyWare. If it's on an isolated test network, that's different, but you would not be able to use Google or any other Internet site from such a network. If your machine has Internet Access, and you log in locally with Admin rights, it's a SEVERE risk.
I'll have to give that method a try: Create new website and then "add: existing website" from source safe. Still, when switching between websites (we _do_ work on more than one website), it gets to be a bit of a pain to have to create a new website and then add from source safe every time we switch.
But surely you only need to set up each site once per machine? After that, you just open the local solution? I'm not suggesting you keep having to create new web sites over and over again. Obviously your machines and network still need to be well configured and consistent or it won't work because the FileSystem paths won't match. You also need to make sure everything is checked in before you switch machines or (again) it won't work.
I can't test this fully, because I only have one client machine left with IIS on it, we changed our main .NET 2.0 dev team over to using Cassini which has solved the complications of trying to manage local IIS servers and their security across multiple machines, but the built-in server does have some limitations - if you want to use ISAPI etc. I did, however, test the scenario you are describing when we first got VS2005 and I don't remember any major problems.
Any why wouldn't I open up SourceSafe on a new machine to "get" the website so I can start working on it? Isn't that what SourceSafe is for (along with change management)?
Yes, but you were asking the question in the context of Visual Studio and saying it was a "bug" in Visual Studio.
(next bit is just for fun)
If you were a real hardcore programmer, you would not even be using Visual Studio, because those guys don't use an IDE and build on the command line!
I'm not working on production Windows Server machines after all: we do our development locally on our Windows XP SP2 boxes before sending it in to QC who then "gets" the code to the staging server where it can be thoroughly tested before being copied to the live servers by operations (only after getting the OK from QC and testing departments). Still sound like amateur hour? We might be low budget, but we're not amatuer.
Interesting that with all this QC they have people logged in with Admin rights and have not designed a proper strategy for how developers are supposed to jump from one machine to another and carry on working. What if one of the hard drives crashes?
--
Gerry Hickman (London UK)
.
- Follow-Ups:
- References:
- Prev by Date: Re: Setup Project Component selection screen
- Next by Date: Re: .cpp Source File
- Previous by thread: Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...
- Next by thread: Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...
- Index(es):
Relevant Pages
|
