Last post Mar 10, 2009 12:33 PM by GaryAF1
Feb 27, 2009 04:29 PM|GaryAF1|LINK
This is also posted under Visual Studio Installation/Setup. Copied here at moderator's request.
Using VS2005/Vista on local computer.
Have VB.Net solution (only 1 project) hosted on remote computer on local intranet. Remote platform runs 2003 Server. Framework 2.0.
Decided to try to do some work without using debugger because I can't get repmote debugger to work.
When I view project in browser (from within VS2005), it comes up but seems to take a fair amount of time to display index page.
When I open VB source behind index page, it comes up acceptably quickly.
When I then attempt to switch to design mode from VB Source, it takes 30 minutes to display the index page, verrrrry slowly building one control at a time.
Seems to be widespread in VS2008 (per forums), but not as much so in VS2005.
VS2005 service pack 1 is loaded.
All worked well using VS2003/1.1 until I converted, all because I had to go to a local Vista platform. Frustrating.
I've already spend tooooo many hours struggling with this. Any thoughts?
Mar 02, 2009 11:20 PMemail@example.com|LINK
Mar 03, 2009 11:33 AM|GaryAF1|LINK
Thanks for the suggestion, but we're already running at 4GB RAM. I would think that should do it.
Mar 03, 2009 11:35 AM|shados|LINK
Mar 03, 2009 03:37 PM|GaryAF1|LINK
Appreciate the comments. I'll attempt to determine if there is a circular assembly resolution issue with my web.config. We've done some more analysis and noted:
1. Every project on the remote Windows Server 2003 development platform that we converted from VS2003/1.1 to VS2005/2.0 (using the VS conversion wizard) is opening pages slowly when we switch to design mode. Two of us developed (and converted) these projects
independently of one another; unless I'm missing the big picture, seems unlikely we'd both have circular references, but I guess it's possible.
2. Also, my coworker created a new project from scratch with a simple page and the page seems to open just fine in design mode -- very quickly in fact. A possible issue with the conversion wizard? Is it possible the conversion created circular assembly
Mar 03, 2009 03:42 PM|shados|LINK
Sorry, circular reference is probably (almost sure) the wrong term here. I just said that for lack of a better word, and I probably confused you instead of helping you.
"Duplicate" references may be a better way to call them? Especially if they were converted from 1.1, and thus were most likely web applications, its possible your references are at the project level AND in the web.config. The ones in the web.config could
be redundant, and send the runtime spinning (and it resolves those when you go to design view).
If the problem is what im thinking of, when you hit design view, the IDE almost freezes, and slowly (painfully so), you see in the status bar at the bottom messages talking about loading assemblies or something. Taking several seconds or more each.
Mar 03, 2009 07:02 PM|GaryAF1|LINK
This is the only reference in web.config to the assembly System.Data. Is this the "possible redundant web config reference" you're referring to? Can't honestly recall if these add assembly statements
appeared in my VS2003 web.config file or not. If this is not the web.config reference you're referring to, what kind of syntax am I looking for?
Mar 03, 2009 10:29 PM|shados|LINK
Mar 04, 2009 10:40 AM|GaryAF1|LINK
I commented out all "<add assembly .." statements in the web.config compilations tag that appear to duplicate the references in my solution explorer. I rebuilt successfully. Unfortunately, the page still comes up slowly with no improvement ....
Mar 04, 2009 11:38 AM|GaryAF1|LINK
Yet another curious discovery. I commented out all of the "<add assembly .." statements in the web.config compilations tag to see what would happen. I rebuilt the solution. Build succeeded. I opened my test page in design mode. Still slow.
I went back to web.config and noticed that -- presumably during the opening of the form in design mode since I didn't do anything else during this timeframe -- 14 of the "system.*" assembles were added back within the web.config compilations tag! Examples:
System, System.Data, System.Design, System.Drawing .....
Do I need to remove references to these assemblies in my solution explorer pane to prevent this duplication?
Mar 04, 2009 06:45 PM|shados|LINK
Mar 05, 2009 01:28 PM|GaryAF1|LINK
We just detrmined that the projects with this problem all use CrystalReports. Furthermore, when I looked at all of my CrystalReports related references, they are all version 9.1.5000.0 instead of 10.2. Apparently, when I converted my project from framework
1.1 to 2.0 using the VS2005 wizard, it didn't bother to do anything with the CrystalReports assemblies. I was unable to see any dual references to 1.1 and 2.0 assemblies as you mentioned in your previous post, but these outdated CR assemblies jumped out at
me. Looks like 1.1 projects not using CR that have been converted are working just fine. Could this cause my poor design performance? What steps do I take to bring CR up to speed using VS2005?
Mar 05, 2009 05:00 PM|shados|LINK
That I unfortunately don't know...the last time I used crystal report was during the .NET 1.1 days, so I never had to upgrade it. You don't have anything in the pages themselves referencing assemblies of different versions? I remember now that that was my
issue, notably with the Ajax Control Toolkit (but has nothing to do with it: it could happen with any controls). Not just between version 1 and 2, but any assemblie that would be referenced twice somehow (that will happen a lot and its normal, but sometimes
you have stuff like version 184.108.40.206 and version 220.127.116.11...tricky stuff)
I looked quickly to see if one of the base config files refered to newer versions of CR, but nope.. so now i'm really at a loss.
If you can't find it at all, then there's the ultimate solution: Make a new, blank project, and copy things one by one over until you trigger the slow design view...then you'll probably have a "OH DUH!" moment :)
Mar 10, 2009 12:33 PM|GaryAF1|LINK
Many thanks to Shados for his excellent suggestions. He, along with post at
http://programminggems.blogspot.com/2006/09/could-not-load-file-or-assembly.html led me to the solution of this stubborn problem. I noticed that there have been numerous hits on this conversation: I can only assume that others have had similar experiences;
therefore, I'll share my experiences for future reference.
1. It's worth emphasizing that my application ran well under Studio 2003 on the 1.1 Framework. The only reason I upgraded to VS2005/2.0 is because my organization has forced us to go to MS Vista on our development clients. Most conversations out there are
now focused on VS2008/3.5. I realize I'm a little behind the curve.
2. I ran everything thru the conversion wizard in an attempt to go from VS2003 to VS2005. I also use 3rd party controls that feature good client-side JScript capabilities since we do a lot of mathematical calculations in grids. These controls required another
conversion process using a wizard provided by their company. I also have 3 pages with Crystal Reports viewer controls on them.
3. My problem was that opening any page in the project in design mode resulted in the page coming up unbearably slowly, building one control at a time (appx 30 sec per control).
Microsoft, in the Crystal Reports for 2005 MSDN article at http://msdn.microsoft.com/en-us/library/ms225442(VS.80).aspx states "...
Is migration automatic?
Yes. That is, if you open a project or RPT file from a previous version in the new software, it is automatically converted to be compatible with the new version....",
when I looked at the references in my solution explorer to anything starting with Crystal," I was still referencing assembly versions 9.1.nnnn.n (compatible with VS 2003). I killed these references and re-referenced, this time pointing to version 10.2.nnnn.n
of the assemblies at C:/Windows/Assembly on my local drive. Still had the problem. I looked at the markup code behind each of my 3 forms that had the CR viewer on them. To my amazement, they still had registration lines near the top that were registering Version
9.1.nnnn.n of the CrystalDecisions.Web assembly! Not seeing much automatic conversion to this point. Replaced these lines with registration of the V 10.2.nnnn.n assembly. Still had the problem. Finally, after stumbling on the conversation at
http://programminggems.blogspot.com/2006/09/could-not-load-file-or-assembly.html I replaced the dlls in my project bin folder (once again Version 9.1.nnnn.n) with the Version 10.2.nnnn.n dlls and suddenly all pages came up very quickly in design mode. Didn't
realize the old dlls in the bin folder played a role since I do not seem to reference them anywhere.
Sure hope this saves you some time and frustration if you struggle with a similar issue in the future ....