Home Dashboard Directory Help
Search

Microsoft.ReportViewer 8.0.0.0 components crash VS when adding reference by emulamer


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 456432
Opened: 5/22/2009 1:51:18 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

When adding references to the 2005 ReportViewer libraries located in \windows\assembly\, visual studio 2010 closes immediately with no errors/crash reports/etc.

Ideally, the assemblies would show up in the .Net tab of the add reference window.
Details
Sign in to post a comment.
Posted by Microsoft on 11/19/2009 at 12:01 PM
Hi Yuri,

Thank you for reporting this. However, it sounds like the root cause may be a separate issue from the one originally filed here. The original bug crashed on adding a reference, whereas you're seeing a crash when building. Could you file a separate Connect bug for the crash you're experiencing? That way your issue will be tracked by an active bug and routed to the appropriate team.

Thanks!
Brittany Behrens
Program Manager, VS Platform - Editor
Posted by YuriYurchenko on 11/19/2009 at 6:03 AM
When I add the MS Report Viewer 2010 references (to assemblies) to the Windows Forms solution, application builds normally.
But when I add a report to the solution and report marked as "Embedded Resource", Visual Studio crashes when I try build the application.

Windows Vista SP2 x64, VS 2010 Beta 2.
Workaround: mark report as [Build Action: None] and copy the report with the application and load from the application location via the reportViewer.LocalReport.ReportPath = "...path to the report...".

Yuri Yurchenko
Sofware Developer.
Posted by Microsoft on 6/4/2009 at 12:42 AM
Hi emulamer,

Thank you for reporting this issue. I've confirmed that this is the same as an issue we are currently working on and tracking with another bug, so I'm resolving this as a duplicate. We plan to fix this crash for the next release of VS 2010.

Thanks for trying VS 2010 Beta1 and sending your feedback!

Brittany Behrens
Program Manager, VS Platform
http://blogs.msdn.com/vseditor
Posted by Microsoft on 5/25/2009 at 5:42 AM
We were able to reproduce the issue you are seeing. We are escalating this issue to the product unit who works on that specific feature area. The product team will review this issue and make a decision on whether they will fix it or not for the next release.
Sign in to post a workaround.