Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / May 2006

Tip: Looking for answers? Try searching our database.

VS2005 - Add assembly reference to asp.net project crashes IDE

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ATGi - 02 May 2006 16:31 GMT
I have an assembly I built which when added to an 2005 asp.net project as a
referenced assembly crashes the entire IDE (this same assembly can be used in
other project types without any issues; it can also be compiled to 1.1, and
included in a 2003 asp.net project without issue). If I reopen and run the
project without touching the references, everything is fine. If I touch the
references for any reason - including changing and saving web.config, or
deleting the offending reference - the IDE crashes. If I delete the
reference, and then touch the references for any reason, the IDE crashes.

I am trying to narrow down what could be causing the crash - I have tried
several other assemblies I have built utilizing various pieces of what is in
the target assembly, and they add without issue.

What processes are at work in the IDE when an assembly is added? What are
possible processes that could be crashing? Is the IDE doing reflection of
some sort on the assembly? If so, what would it being looking at? I need to
find a way to duplicate this problem so I can figure out the cause.

TIA
"Gary Chang[MSFT]" - 03 May 2006 07:27 GMT
Hi,

Thank you posting!

Before we digging into this problem, would you please provide more detailed
info about it?

1. How about that assembly, a strong named one in VB2005 or C# 2.0?

2. Do you mean if you don't touch that reference in VS2005 IDE, then it
could work well with your VS2005 asp.net project?

3. Have you tried to add it to another VS2005 asp.net project, does this
project occur?

4. Have you tried to delete that reference outside VS2005 IDE--modify the
web.config file in a text editor directly?

These tests will help us research your issue, so I appreciate your time in
performing them. Let me know the results at your earliest convenience. If
you have any questions or concerns, please let me know. I am standing by to
help you.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
ATGi - 03 May 2006 16:19 GMT
Thanks Gary,

1. It is a strong-named assembly and the project language does not matter.
The assembly also has been obfuscated and is not IL-only. This seems to be
only part of the issue because other assemblies obfuscated in the same way
don't fail. However, this assembly doesn't fail when it is not obfuscated, so
it has something to do with it.

2. Correct, everything will compile and run correctly, it just seems that
something happens when references are updated.

3. Yes, any asp.net project will dump the IDE when this assembly is
included. This has been confirmed on multiple machines. However, non-asp.net
projects have no problems.

4. The web.config does not contain a reference to the assembly, that only
seems to happen when the assembly is in the GAC. In any case, if I add it to
the GAC, and then edit the file, it doesn't matter.

Thanks again for your help in this matter,

Jeff.

> Hi,
>
[quoted text clipped - 30 lines]
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary Chang[MSFT]" - 04 May 2006 07:30 GMT
Hi,

Thank for your detailed response!

I am afraid this is may be a product issue. We have some similar cases
about that Visual Studio 2005 IDE crashes when it attempt to parse some
informal (not match the naming convention) IL code in an assembly. It seems
that assembly's obfuscated IL code happens to fire this trigger.

I apologize for any inconvenience this may cause you.  If you would like to
make a suggestion on how to improve our products please provide your feed
back at:

http://lab.msdn.microsoft.com/productfeedback/default.aspx

Our development team may communicate with you directly on the issue there.

Thanks for your understanding.

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.