VS.NET won't let me open a C# web application solution file unless I am connected to the internet. I am slightly annoyed but mostly confused.

While on the train, I open up VS.Net 2003, it tries to open a project called forecast. The Open web Dialog box appears ...

"http://localhost/forecast"

I get an error message unable to connect. IIS is on and everything works fine if I have an internet connection.

Any ideas? Thanks.

Hey,

No idea? Does this project use an external resource, like a web service, or something along those guidelines?

You should be able to run it locally without internet service...

Brian

There are no external resources being used at all. Totally average web application.

I just noticed under projects that I can set it to work off-line. I'l try that. I have combed all the application config files trying to find a setting so it must be in VS.NET itself.

This is the kind of stuff that is so frustrating. I don't need them to configure my web server so that it runs tha application on a build. Let me do it myself!

Thanks again

I figured it out.

If you are having this problem:

Project | Web Project | Work Offline

Then

Project | Web Project | Synchronize All Folders

Do this while you have an internet connection. If you close and open VS you will notice that it doesn't try to run the Open Web Dialog and connect to http://localhost/project name.

Sean

I did a test with my machine disconnected from my network. I loaded a solution file that contains a VB.NET web application and a C# web application. I did get a couple errors because all my projects are under source control and it tried to update the status of the files. Apart from that, they loaded fine.

Are your projects under source control? The only other thing I can think of Brian already mentioned. You shouldn't need to work "disconnected". Is it possible there is some security issue and your machine is trying to authenticate you against a domain?

Thanks.

It works if I make sure to check Work Offline in the Project --> Web Projects menu. I am not sure if this is a VS.NET 2003 issue because I have never had the problem before.

There is no funky authentication and I am not under source control.

Thanks again,

Sean