Problems running web applications in Visual Studio 2003

neetw · Post by **neetw** » Mon May 30, 2005 12:59 pm

Hi,
I have successfully downloaded my solution from Vault into Visual studio 2003.
I made a few changes to some of the aspx pages, and rebuilt the solution.
When i ran the solution, i couldnt see any of the changes i had made to the pages in there. Only the changes in web.xml were reflected on the page (since the database connectivity path is specified in there.)
I tried adding breakpoints, but it didnt stop at those breakpoints. Hence i am unable to debug my application.

Is there something wrong with my setup?

Thanks,
Neet

dan · Post by **dan** » Mon May 30, 2005 1:36 pm

It sounds like the solution is not running the exes that you are actually changing. If this is a web project, verify that the virtual folder is pointing to your current working folder (perhaps there is an old copy somewhere that the virtual folder is pointed to?)

neetw · Post by **neetw** » Mon May 30, 2005 9:11 pm

Hi Dan,
So far the changes i made were to the Controls and some cs files, and these were not reflected when i started the web application. Whenever i update the aspx page, just to print something like a textbox or something, i get an error as below.

The min i uncheckout the aspx page it all works fine.
I had deleted the virual directories, etc before downloading the solution.
But it does pick up the changes i have made to the web.xml. I am not sure what the problem could be.

I tried the same with another application that i downloaded from Vault and it works fine there. Its just not working properly for this one application.

Source Error:

Line 217: base.OnLoad(e);
Line 218: if(!this.IsPostBack) {
Line 219: guid.Value = Guid.NewGuid().ToString();
Line 220: }
Line 221: }

Source File: c:\inetpub\wwwroot\IMUser\Classes\PageBase.cs Line: 219

[NullReferenceException: Object reference not set to an instance of an object.]
Six88.ImageMarket.UI.PageBase.OnLoad(EventArgs e) in c:\inetpub\wwwroot\IMUser\Classes\PageBase.cs:219
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750

dan · Post by **dan** » Tue May 31, 2005 8:04 am

Hmm - this doesn't really make much sense.

When you check out and edit the file, check its status in the Vault GUI client. Does it report it as edited?

Is the .aspx file in the same folder as all the other files that do work?

Is this the only file with that problem, or do all files of type .aspx have this problem?

Finally, if you try this from a different machine or login as a different user and use different working folders, do you get the same results?