VS.NET not responding when opening .aspx file in design view

bwagner · Post by **bwagner** » Tue Feb 24, 2004 5:17 pm

I have a problem with opening an .aspx page whenever our solution is bound to Vault.

The end result is always the same if integrated with Vault: I am unable to open .aspx files in "Designer View" (HTML/Design View). VS.NET locks up, the cpu pegs, and I have to start all over again.

I have used three methods for opening the solution, which is in Vault on a Windows Server 2003 machine. The solution has 11 projects, most of them small.

1) Within VS.NET, File-->Source Control-->Open From Source Control and browse to the solution in question. The solution loads just fine, builds just fine, but I try to open an .aspx file in Designer View and ... *crash*.

2) After deleting all existing folders containing the solution files, I start over using the Vault client this time. I do a get of all the files into their respective folders locally, and double-click the solution file, which opens in VS.NET. After loading all the projects, I get, and ignore, a warning about the MSSCCPRJ.SCC file being absent. I choose File-->Source Control-->Change Source Control and bind the projects to Vault one-by-one. After dealing with what comes along with that, I try to open an .aspx page in Designer View and ... *crash*

3) Same as above, except I elect NOT to integrate with Vault (by binding). I can open .aspx files without seeing any problems.

So, essentially, I cannot work on .aspx files while VS.NET is integrated with Vault - I have to utilize the Vault Client concurrently.

VS.NET 2003 (v.7.1.3088)
WinXP Pro SP1
Vault v.1.2.2

Thanks.

-BW

dan · Post by **dan** » Tue Feb 24, 2004 10:54 pm

Does a dialog come up before it crashes with anything helpful in it?

ericsink · Post by **ericsink** » Wed Feb 25, 2004 8:45 am

I've heard this report once before, somewhere on USENET I think.

During the 2.0 development cycle, I tried at great lengths to reproduce the problem and could never make it happen. If we could reproduce it, we'd obviously like to fix it.

Guest · Post by **Guest** » Wed Feb 25, 2004 10:29 am

dan wrote:Does a dialog come up before it crashes with anything helpful in it?

Unfortunately, no. Basically, I'll double click a file, and watch my cpu usage, it takes about 10 seconds for it to finally stop responding. This happens regardless of whether the Designer View is set to open in HTML View or Design View (VS.NET Tools-->Options-->HTML Designer/General)

Guest · Post by **Guest** » Wed Feb 25, 2004 10:36 am

ericsink wrote:I tried at great lengths to reproduce the problem and could never make it happen. If we could reproduce it, we'd obviously like to fix it.

That's another problem, we've got 5 developers here. Three of us have seen this problem intermittently and in no apparent pattern. It's terribly annoying. We'll work problem free for a couple months and then we'll "catch" this problem and it stalls us for a few days while we try and work around it. I've gotten to the point of working sans integration, but it's obviously less convenient and more mistake prone.

I believe one of my coworkers has spoken with somebody at SourceGear, and they suggested a workaround of deleting the VSWebCache folder which pertains to the offending project, as well as possibly deleting the solution's .suo file and recreating the project's web root. This workaround doesn't help me.

ericsink · Post by **ericsink** » Wed Feb 25, 2004 3:33 pm

Anonymous wrote:
ericsink wrote:I tried at great lengths to reproduce the problem and could never make it happen. If we could reproduce it, we'd obviously like to fix it.
That's another problem, we've got 5 developers here. Three of us have seen this problem intermittently and in no apparent pattern. It's terribly annoying. We'll work problem free for a couple months and then we'll "catch" this problem and it stalls us for a few days while we try and work around it. I've gotten to the point of working sans integration, but it's obviously less convenient and more mistake prone.

I believe one of my coworkers has spoken with somebody at SourceGear, and they suggested a workaround of deleting the VSWebCache folder which pertains to the offending project, as well as possibly deleting the solution's .suo file and recreating the project's web root. This workaround doesn't help me.

These kinds of problems are the worst. It's bad enough that it's intermittent and we can't reproduce it at all. The other problem is that there is simply no conceptual reason for the problem. There's no reason Vault should even be involved in opening an ASPX page.

If you had told us that your coffee pot stopped working right after you installed Vault, I would have exactly the same amount of insight into what might be causing the problem.

Nonetheless, we believe you.

We can keep trying to reproduce this, but if nobody but you ever sees the problem, it's going to be very difficult to fix.

bwagner · Post by **bwagner** » Wed Feb 25, 2004 5:24 pm

Nonetheless, we believe you.

Yeah, sure ya do.

Thanks for the responses.

isamu.ybarra · Post by **isamu.ybarra** » Fri Jan 05, 2007 4:10 pm

Sorry to dig this up from the grave, but was curious if anybody else has/is experiencing anything like this and/or has found a resolution/cause.

I have unfortunately just recently become plagued by this *exact* same behavior, on a development machine that I have been working on for 2 years+, all of a sudden. To make matters worse, I have completely wiped my machine clean and reinstalled to a different OS (Server 2003 to XP) with no luck, the same problem occurs.

Just as this original poster mentioned, if my project is not bound I am able to open .aspx files with no problems. However, any files that are bound will "hang" vs.net 2003 and the cpu will spike to 100%. We too have 5 other developers who are experiencing no problems, it is localized to my machine (lucky me).

I have only installed a few programs on this clean box, office 2003, studio 2003, and thats pretty much it other than the prereqs for those programs.

I am already in talks with support on this befuddling issue, but wanted to pursue all avenues possible. Everyone here at the office is as perplexed as I am.

Thanks,

Isamu

lbauer · Post by **lbauer** » Fri Jan 05, 2007 4:33 pm

I'm the one you spoke with from Support.

I did find more information about this in our support email history.

One user reported:

When the IDE hangs, our best workaround is to force quit VS.net and open the code-behind of any aspx page in the site, and change it to inherit from System.Web.UI.Page. Then, open the aspx page in the VS Designer window. It will open without hanging. Now, change the code-behind class to inherit from our PageBase class. Now reopen the aspx page and it will not hang! This seems to allow the IDE to get passed the compilation phase where it fails. However, while this workaround will last a little while, the symptoms will soon reappear, perhaps when you recompile the solution, or when you open and close the solution again! So the workaround is short-lived.

SourceGear Support had another workaround:

In your project that inherits from UI.Page, go to References->System.Web, and toggle the "Copy Local" property to False. We suspect the problem is some kind of locking issue when copying the system dll from the GAC. It may be Vault related, or since Vault is a managed app being called from within the unmanaged VS.Net application, it may be an platform issue between the two.

Another suggestion was that if the Copy Local property was already "False," toggle it to "True."

If none of this helps, we'd like to see copies of your IDE and server logs.

isamu.ybarra · Post by **isamu.ybarra** » Fri Jan 05, 2007 5:03 pm

Thanks Linda,

I tried both of these possible solutions repeatedly to no avail, I am still attempting other things in the meantime, and appreciate your assistance.

Isamu

isamu.ybarra · Post by **isamu.ybarra** » Fri Jan 05, 2007 5:11 pm

Wow... I found it.

I was thinking about what was different from my box and all the others here with this clean install, and the only thing that came to mind was they had installed a VS addin called Resharper.

I had this on my box previously before my reinstallation, but it must have somehow got corrupt leading to this perplexing problem. So after I installed it, voila, problem solved.

Well, at least the good thing that came out of this is that if other people ever experience the same problems, they should look in this direction or any other vs addin could be the culprit.

Thanks,

Isamu