Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...



Hi Owen,

No. Not helpful. I need to be able to work on and DEBUG my website using a URL, not just "localhost" or "localhost:port". Part of the security on our website requires that the URL be correct.

Perhaps this app needs a redesign?

We are not using the Team edition of VS2005 because of the CO$T.

We don't use it either.

> We are a
small shop with individual developers working on Windows XP Pro and then moving the code to Windows 2003 Servers for final testing and then production.

More stuff interspersed below:

My news client has stripped out the rest of the text so I'll make headings, are you sure you're posting in plain text and not HTML?

> Sounds like amateur hour?
> ? Name-calling? You're not being helpful: just RUDE!

OK, it's not name calling (that would be a personal attack), it's really to establish what kind of setup we're dealing with, it's not meant to be rude. Remember those annoying error messages that say "consult your Network Administrator", well unfortunately sometimes that's the correct thing to do. The reason I asked the question is because some tell-tale signs in your post made me think this is not a well configured Enterprise network? The biggest give-away is when people log in with Admin rights - in my view that makes it "Amateur Hour".

The other things I'd not expect to hear in a pro setup were "opening up SourceSafe" and "going into IIS manager and setting the root directory".

So anyway, you clarified you tried it from within VS2005 but didn't give very good details of the exact screens you encountered and what you did in each dialog? You also didn't make clear the exact folder structure of the IIS servers that reside on your multiple client machines and the configuration thereof?

On my system, I create a local solution, then "Add : Existing Website" and then choose "Source Control", I can select a FileSystem folder at that point, but because I have properly configured HTTP, I can also choose to add it to the local IIS server with a tick box. Did you see that tick box in your dialog, and does it work as expected?

I'm running VS2005, but I run SourceSafe 6.0 at the moment - I don't know if this affects anything. Are you running VSS 2005?

--
Gerry Hickman (London UK)
.



Relevant Pages

  • Re: deploying website VS 2005
    ... Thank you for explanation but I'm trying to run my website and get error: ... Server Error in '/' Application. ... An error occurred during the processing of a configuration file ... you must uninstall the WAP add-on first! ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: [IIS 6] A summary of my strange situation
    ... security-related configuration, so maybe someone can help me out of this. ... Then I created new subdirs for every website I'm ... other website or subdirectory I try to enable Windows authentication on ... administrators, web developers and SYSTEM, and I gave read permissions to ...
    (microsoft.public.inetserver.iis.security)
  • Re: Livna Usability Assessment (Was: Re: cursed nvidia fedora my lack of knowledgeness)
    ... > The website really isn't the point here. ... give you the information needed to accomplish much. ... "How to enable the Livna repository on your system". ... that's Configuration, but we're both too technical to understand others ...
    (Fedora)
  • [IIS 6] A summary of my strange situation
    ... security-related configuration, so maybe someone can help me out of this. ... OWA on my domain's main website), then I created a "web sites" dir on my D: ... other website or subdirectory I try to enable Windows authentication on ... administrators, web developers and SYSTEM, and I gave read permissions to ...
    (microsoft.public.inetserver.iis.security)
  • RE: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...
    ... When you need to create a new website (or copy an existing website from one ... IIS Manager Default Root Directory depending on what site they're on. ... I added it to SourceSafe. ... "Change Source Control", but there the files are all under SourceControl. ...
    (microsoft.public.vsnet.general)