So, is it the combination of your dll and the commercial dll that causes the hang in vs2010?
It seems like you're affected by two issues at once; a crash in the commercial dll is initating the debugger, and vs2010 isnt handling that correctly. So it seems like we can just claim there is an issue with the commercial dll, but I'm probably missing something. I really can't say anything useful. The commercial dll; is it publically available? What is it? Is it definately built for .net 4? Does it work when attached to other non-webforms projects? (Say, a console application)? What does it do? Did you have to install anything, or is it just as-is? How much code is required, and what is it, to generate this issue from scratch? On Tue, Jan 25, 2011 at 12:46 PM, Glen Harvy <[email protected]> wrote: > Thanks for responding .... > > I have tried a completely new web forms project and it is that project I am > now trying to get working. The only thing that I add to the new project is > my dll and then as another test the commercial dll. The result is the same. > > I have the source for my dll however this is no longer the sole issue. The > commercial dll has the same affect as my dll. > > I also distribute this web forms site as a built-in web server so including > my source is not my desired option. > > mmmmmmmmmm..... > > On 25/01/2011 12:25 PM, Noon Silk wrote: > > It's hard to answer this as-is I think. > > Can you try starting a totally new webforms project and check if you can > reference the dll there? > > What is the dll? The person on the asp.net forum was asking you to add a > reference to the project instead of the dll, on the assumption you actually > have the source for the project (that generates the dll). Do you? If so, > including it in your solution, and just adding a reference to it, will be > fruitful, but may not be possible. > > > On Tue, Jan 25, 2011 at 11:42 AM, Glen Harvy <[email protected]> wrote: > >> Hi, >> >> I have asked this question in the asp.net forums as well as stackoverflow >> without any success and I am hoping that someone could help me out. >> >> First of all I just changed my Target Framework from 2 to 4 in a asp.netweb >> forms application that was working perfectly well in asp.net2 and now I >> have this problem. >> >> My post on asp.net <http://forums.asp.net/t/1645923.aspx> has all the >> gory details but essentially I have created a new Web Forms application in >> VS2010 that targets .Net4. It runs fine in the developer web server - it >> should as there are no changes :-). I then add a reference to a dll that I >> have compiled for .Net4 and VS2010 freezes. When I use Task Manager to shut >> VS2010 down I get the following error messages. The message regarding the >> source file is not displayed until I run Task Manager to shut VS2010 down. >> For testing purposes, I removed that dll and added a reference to a >> commercial dll compiled that targets .Net2 with the same results. >> >> Can anyone suggest what I am doing wrong. >> >> [image: Error Messages] >> >> Thanks - any and all suggestions appreciated ..... >> >> > > > -- > Noon Silk > > http://dnoondt.wordpress.com/ (Noon Silk) | http://www.mirios.com.au:8081> > > "Every morning when I wake up, I experience an exquisite joy — the joy > of being this signature." > > -- Noon Silk http://dnoondt.wordpress.com/ (Noon Silk) | http://www.mirios.com.au:8081 > "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
