Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...
- From: Owen <Owen@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 31 Aug 2006 06:42:01 -0700
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.
We are not using the Team edition of VS2005 because of the CO$T. 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:
--
Owen
"Gerry Hickman" wrote:
Hi Owen,? Name-calling? You're not being helpful: just RUDE!
I've created a dot-net 2.0 Web Site on one machine using Visual Studio 2005.
I created the site by selecting "Create/Website" "ASP.NET Web Site" Browse...
"Local IIS" "Default Web Site".
Sounds like amateur hour?
After I finished the site, I added it to SourceSafe. No problems so far.
OK.
However, I wanted to work on the site on another computer.
OK.
SO, I opened up
SourceSafe and did a recursive get of the project to a directory
?? "Opened up SourceSafe" ??
Can you clarify this part, you mean outside the VS2005 IDE?
The first time, yes VSS outside the IDE. Tried again (scrubbed destination
directory) and did an "open from SourceSafe" insdie VS2005 IDE with exactly
the same results.
> on the new
computer; opened IIS Manager and set the root directory of localhost to that
root directory created by SourceSafe;
Sounds like amateur hour again?
AGAIN, RUDENESS and NON-HELPFUL comments! I came here to get questions
answered, NOT to be called names!
opened VisualStudio 2005; logged into
SourceSafe within VS2005; BUT ALAS, none of the files were marked as locked.
Hmmm.
I found a thread that said something about localhost.sln and localhost.suo
and deleting them, but that seems to change nothing.
Were they pros of amateurs?
MSCP's are not supposed to be amateurs.
Why isn't this easy?
Have you considered a crash course in team development strategy, network
protocols and security best practice? If you used IIS manager, it
probably means you are logging into your machine with Admin rights, this
is VERY bad for security!
We're developing on our local machines. When Microsoft makes it possible to
do actual work on a machine with less than admin rights, then we'll do it.
Until then....
One option you may want to consider for simple web sites is using the
VS2005 built-in Cassini web server, this will avoid any issues with IIS,
vDirs, server extensions and it also works with user rights and makes it
much easier to switch machines.
NOPE. I haven't found a way to use the Cassini server and still be able to
specify the URL (name.domain.com). The site depends on the URL for part of
its security, etc.
If you decided you MUST have IIS local then you may want to get a guy
like me to set up all your computers, network, server extensions etc.,
and provide training for each developer.
If you don't like any of those options (and insist on using proprietary
NetBIOS/SMB), just make an effort to understand how absolute and
relative paths work - both in the FileSystem and the vDir.
If you like open-standards (like I do) set it up to use HTTP instead.
We are using HTTP.
--
Gerry Hickman (London UK)
Can you get down off your "I'M SMARTER THAN YOU" soapbox now and make some
comments or suggestions that might be helpful?
.
- References:
- Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems....
- From: Gerry Hickman
- Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems....
- Prev by Date: Re: Can't develop unmanaged VB with VS.NET 2003?
- Next by Date: Checking out/opening .sql file?
- Previous by thread: Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems....
- Next by thread: Re: SQL 2005 or SQL 2000?
- Index(es):
Relevant Pages
|
