Visual Studio 2012 crashed while adding data source to report viewer - asp.net-mvc-4

I am trying to create rdlc report in vs 2012 ultimate. report was working fine on vs 2010. Now problem is: Visual studio crashed (closed) when I try to add data source in report viewer.
any suggestion to resolve this issue. Is this a known error in vs 2012 ultimate ?

I was with the same error, then I removed the PdfSharp and MigraDoc libraries from the project.
No errors anymore.
EDIT:
Actually, the error was in the source control.
PdfSharp.Charting was removed but the project still was refer it.

Unfortunately this is a known issue in both Visual Studio 2012 and Visual Studio 2013, it is mentioned in this Microsoft Connect bug.
A workaround has been posted on this MSDN blog.

I also had this problem. I was able to add reports to a new project so I knew there was a problem with my project. After much trial and error I determined that I had some unnecessary references that got carried over from an older project. The references were not correct and were missing some dependencies. After deleting these references my problem was resolved.

I encountered this fault after migrating a project from VS2010 to VS2012 recently.
The fix that work for me was to open the .rdlc in a text editor, and look for the tags that contain the path to the dataset used in the report. They looked like this:
<rd:SchemaPath>.......some path.....</rd:SchemaPath>
In my case the path was the old path to where the source was previously kept when I was working in VS2010. I had changed the location of the project on my PC and this path was now invalid.
So I updated the path to the correct location, saved the RDLC, and everything works fine.

I debug and found that if you download VS- Command the problem is resolved

Related

Migrating SSDT from 2015 to 2019 Breaks Script Component

I just migrated from SSDT 2015 to SSDT 2019 and tried to open a project created in SSDT 2015. One of the packages has a data flow task with a script component in it. The script component fails to build with the error:
Could not find part of the path
'C:\Users\xxxxxx\AppData\Local\Temp\2\Vsta\c2e811fdc5974e2ca3f7cb5426c82033_out'
I tried to delete the .vs folder in my project but that didn't work. The script still fails to rebuild. The script has a lot of classes in it so I'd rather not start from scratch and copy everything into it. Any idea what could be wrong?
Appears this issue may be caused by an incompatibility between Visual Studio 16.9 and SQL Server Integration Services Projects. The issue is described here: https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects
Recommendation is to regress back to Visual Studio 16.8 or earlier.
The new version of data tools fixed it for me without rolling back to 16.8. This was a difficult issue to resolve. Nowhere in the MS documentation do they mention the tools update fixes that specific error. Thanks for the link!

Visual Studio 2013 crashing when opening XAML

I have a C# WPF project I can open just fine in VS 2010 Ultimate or 2013 Ultimate.
I can edit it and run it from either.
When I double click the window.xaml, it crashes 2013.
I disabled then uninstalled my extensions. Still crashes.
I spent more than half the day uninstalling (uninstall is broken, btw) and re-installing VS 2013 Ultimate. Still crashes.
Per comment, here's a screenshot of the error:
Actually just tried to create a clean WPF project and it crashes the same way while attempting to create a new WPF project.
Always check this folder for any VS errors
%APPDATA%\Microsoft\VisualStudio\PUTYOURVSVERSIONHERE\ActivityLog.xml
If the folder doesn't exist or is empty, run Visual Studio with this command:
devenv.exe /log
There could be many reasons. This one for example was because of an outdated driver. There may be workarounds, however which one to use will depend on the error you see. Can you update your question with the error message?

Visual Studio Tools for Office VSTO "customization assembly could not be found or could not be loaded"

I just installed Visual Studio 2012 Ultimate and I am trying to create a managed code extension project for Excel 2010 (32 bit Office Professional Plus). I have tried using the .NET 4.0 template contained in VS Ultimate for an Excel 2010 workbook. When I create the project everything looks fine until I run it.
Excel opens and I get the error message "The customization assembly could not be found or could not be loaded. You can still edit and save the document. Contact your administrator or the author of this document for further assistance." The details section is blank.
I have tried everything I could think of to figure this out and I have run out of ideas. I removed all addins from Excel except for the VSTO Design-Time Adaptor for Excel. I removed all personal macros. I set every directory I could think of to "trusted" in Excel and lowered the security settings for all options to "enabled (not recommended)". I completely uninstalled Visual Studio and re-installed. There are no errors or warnings showing up in Visual Studio. I also checked to make sure ".NET Programmability Support" was installed for my copy of Microsoft Excel.
I would link my code but I haven't written anything. I can't even get the default template to load when I run the project. A few others at work have the same setup as me and VSTO runs fine for them using the same steps. I even had someone send me a working project but it gives me the same message when I try to run it.
Is there anything else I can check to see where the problem is occurring? I tried setting break points in the project but it is failing before it gets to any of them.
Thanks so much for your help.
I've run into the same problem with Visual Studio 2010.
I isolated the problem to an SSRS reporting link we were trying to run from the add-in. I removed all the reporting stuff (service reference, sub-dirs, etc.) - the add-in runs fine.
We just ran into this and discovered that a method had a system exception that was not handled. It was hard to track down but once the culprit method had an exception handler the customization finished loading properly.

mvvm-light : losing intellisense on VS2012

We are using MVVM Light Toolkit (from Galasoft - Laurent Bugnion).
Until now we were using Visual Studio 2010.
Everything was working well (thanks to Laurent).
Two days ago we moved to Visual Studio 2012.
And now Intellisense is no longer working in Xaml files (but still working in code-behind).
After looking on forums and made some tests, it appears that we have an issue with "GalaSoft.MvvmLight.Extras.SL5.dll".
As soon as GalaSoft.MvvmLight.Extras.SL5.dll is removed from project references, intellisense is working again.
Someone already had same problem and/or know a solution ?
Thanks.
Alain.
We had a similar problem when we migrated from Silverlight 4 to 5. We were using a local copy of GalaSoft.MvvmLight.Extras.SL5.dll copied from another computer.
Once we installed the MvvmLight .msi package and changed the reference in our Silverlight project to C:\Program Files (x86)\[...]\GalaSoft.MvvmLight.Extras.SL5.dll, IntelliSense started working again.
Hope this helps

vs 2008 broken snippets functionality

Is there a way to reset to the original vb.net snippets that came along with visual studio 2008?
I recently installed a purchased third party lib, that managed to break almost all the default snippets.
I can see that the snippets do physically exist in C:\Program Files\Microsoft Visual Studio 9.0\VB\Snippets\1033 but only the following sections are loaded to vs 2008:
application
office development
os
wpf
Any help would be appreciated...
Found a solution !!!
I went to tools > Code snippet Manager
and re-added the C:\Program Files\Microsoft Visual Studio 9.0\VB\Snippets\1033 folder
Everything works great now !!!
You can try to reset the IDE-settings by calling it with /resetsettings
It sounds like your SnippetIndex file is broken. There should be a file at the directory you listed named SnippetIndex.xml. This is the file that is consulted in order to build the initial list of snippets. Can you check that file and see how big it is. It should be at least 500+ lines (mine is 579).
If it's less then this is almost certainly your problem. You can fix this by repairing the Visual Studio install
Go to Control Panel -> Add Remove Programs
Select Visual Studio
Choose Repair