Previously Ive used Object Exporter to export object content to various formats to aid in debugging, it helped enormously. Unfortunately it wont work in vs2019. Does anyone know of a similar tool that will work in vs2019 ?
You should compile de latest version or simply download the 2019 October compiled version from this Github comment;
There is not other tools in visual studio extension marketplace.
Maybe you can download the source code, then rebuild it for visual studio 2019.
Update 2022:
I've published free and open source extension Object Dumper for Visual Studio and Visual Studio Code under the MIT license.
"Dump as" commands are available via context menu in the Code and Immediate windows.
It's exporting objects to:
C#,
JSON,
Visual Basic,
XML,
YAML.
I believe that combined with the Diff tool it can be helpful.
Related
I have a windows form project and I want to create an installation package for this project. How can I create a setup file in Visual Studio 2012 ? My project is without data base.
How to create a Setup package using Visual Studio 2012.NET?
Microsoft released the Visual Studio Installer Project extension in April of this year, the catch is it's for VS2013, not VS2012.
http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx
The 'lite' InstallShield option remains in VS if you need something with more flexibility.
Advanced Installer also has a free version that includes an extension for VS. This is a commercial tool but the extension is included in the free edition as I said, for more advanced features you need to purchase a Professional or higher licenses and edit the project direct from Advanced Installer GUI, not from VS. (but you can still use the project in the VS solution, so you get the MSI built at the end of your build process)
Visual Studio setup projects (vdproj) are not supplied with VS 2012
There are several solutions for you:
You could use InstallShield instead.
If you don't want or
can't use InstallShield for any reason, you could try WiX. This
toolset builds Windows installation packages from XML source code.
If you only use Windows Presentation Foundation (.xbap), Windows Forms (.exe), console application (.exe), or Office solution (.dll) you could look at ClickOnce. To use this you should right click on the project file in the solution explorer and select "Publish" from the pop-up menu.
Alternatively you can use previous version of Visual Studio (2010).
We developed an application in visual studio 2010 and reports are working fine, when we choose to open the same application through visual studio 2012 Ultimate, reports are not working and when i open .rpt file showing binary format ad also I could not find Crystalreport.rpt in Reporting template in visual studio 2012. After googling it, I have installed
CRforVS_redist_install_32bit_13_0_5 , but doesn't work.
How can i change or edit .rpt file design using visual studio 2012 and want to change the .rpt database name too. Any suggestion or idea to achieve this?
I had the same problem after installing visual studio 2012 and found no answer on the forums. I uninstalled CR yesterday and downloaded again the CRForVS 13.0.5 from here just in case there was a bug in the previous version I downloaded in may and installed it. Then I installed update 3 for Visual studio and everything works fine now.
Cheers
Michael
I figure this one out for me.
From SAP Crystal Reports's download site:
Please note: To integrate "SAP Crystal Reports, developer version for Microsoft > Visual Studio" you must run the Install Executable. Running the MSI will not ? >fully integrate Crystal Reports into VS. MSI files by definition are for runtime >distribution only.
By default Windows 10 does not install the 3.5 framework, CR for VS still needs >it. Select it by "Turn Windows feature on or off" and choose both options.
I downloaded the exe, instead of the MSI packages, and it worked for me finally. Helps to read I guess.
I have installed the CRM 2011 SDK addin for visual studio 2012 (ultimate) and am trying to create a XAML Workflow Activity
I have added the CRM Workflow items to the toolbox using these instructions Add Microsoft Dynamics CRM Workflow Activities to the Toolbox
When I try and drop a Workflow on the design surface it say in red text "Could not generate view for Workflow"
Hovering over the text reveals a System.IOException that says "Cannot locate resource workflowdesigner.xaml"
How do I fix this?
You probably need to refer to the assemblies from VS. It's a bit of pain but a healthy conduct. In VS12 it's made a bit easier (finally, after a decade) to copy references from another project and (really, really finally) to refer to several DLLs at the same time.
It's the best practice and prefer conduct. :)
I fixed this by dumping the contents of my CRM SDK bin directory (about 24 assemblies) into C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PublicAssemblies
Not elegant but obviously there was a dependency in there somewhere.
Ondra is correct, this is a problem with the latest version of the SDK. Version 5.0.9690.3448 of the microsoft.xrm.sdk.workflow.dll does not work, whereas version 5.0.9688.1533 does not present the issue.
I had this issue occur on a XAML workflow that I previously had no problems with, and the issue turned out to be the upgrade of the SDK file.
Visual Studio 2012 Update 2 does not have any effect on this issue.
This example (and whole CRM workflow) under VS works properly only with CRM SDK version 1.0 - latest version 1.1 and version for VS 2012 causes described problem.
OK, I also hit this problem and made it work with your hints, I reached this result:
Changing VisualStudio version had no effect.
Changing the SDK version actually worked!
I am using SDK for CRM 2015 with version of 7.0.0.43 with visual studio 2015 and 2017. You can download it directly or use Nuget For "Microsoft.CrmSdk.Workflow" and "Microsoft.CrmSdk.CoreAssemblies"
SDK for 2018 (8.0.0) and Dynamics 365 (8.2.0.49) did not work.
Also Visual Studio 2012 Update 2 fix this problem
The CVSI (Castle Visual Studio Integration) (which was available up to VS2010) was a good solution for handling NVelocity content files. There is no version for VS2012. Is there any other Extension for VS2012 out there to handle NVelocity content? Adding .vm extension support via the HTML editor is a temporary solution to provide some support for formatting the HTML in the content...but not the NVelocity code.
I actually upgraded CVSI for Visual Studio 2012 towards the end of last year, however I never published it because I couldn't work out how to make a single .vsix support both VS2010 and VS2012 so I could upload it to the Visual Studio Gallery.
I'm happy to email you (or upload) a preview .vsix that you can try out and let me know how you go. Since there is still interest in CVSI, I'll try to find some time over the next few weeks to get the updated version up on the gallery.
Edit 2014-05-25: I've released 0.5.0 with support for Visual Studio 2012 and 2013, you can download them here: http://jonorossi.com/projects/cvsi/
I opened my vs2010 solution with vs2012 but it didn't make any conversion as from 2008 to 2010 was happening. So my solution still remains the same as 10 label on it. when I make a new solution of course it has 11 label on it. I haven't got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution?
I managed to 'convert' the solution file to change the line containing '# Visual Studio 2010' to '# Visual Studio 2012' in the .SLN file.
Manual editing of the solution file is not necessary, or recommended. Simply open the VS2010 solution in VS2012, left-click the solution (at the very top of the Solution Explorer), then use File | Save As to overwrite the original file. This will effectively convert the VS2010 solution file to a VS2012 solution file.
There are some exceptions, but mostly you'll be able to open the same project and solution files files in both VS2012 and VS2010 SP1.
VS2012 may convert projects when you first open them, but the changes are (except noted in the document linked) backward compatible with VS2010 (ie using conditionals where needed to only apply to either version when loaded) Most project types will be left entirely untouched though.
It is about Visual Studio 2012 Compatibility
If you created your assets in Visual Studio 2010 with Service Pack 1 (SP1), many of them will load and run in Visual Studio 2012 without any further action on your part.
Many assets will also open again in Visual Studio 2010 with SP1 without any issues, even after you open those assets in Visual Studio 2012
For C++ projects it makes a difference, as the 2012 compiler (VC11) will only be used on projects that are explicitly 2012, not on 2010 projects opened in VS 2012. Some C++11 improvements are available with the VC11 compiler but not with VC10 (see this SO Answer for a summary), including:
Range based for-loops
New standard library headers (atomic, mutex, thread,...)
Smaller standard library container sizes
(And more to follow when the Nov 2012 CTP is delivered to VS 2012)
In order to convert from VS 2010 project to VS2012 there is no need to manually edit the solution file or 'Save As' over the existing project. Instead:
If you decline the update when first prompted, you can update the project later by opening the Project menu and choosing Update VC++ projects... [at the top of the menu options]
From MSDN's "How to: Upgrade Visual C++ Projects to Visual Studio 2012"
(This page was linked from #Joachim's MSDN link, but I wanted to have the answer here on SO since a number of other answers suggested manual workarounds instead of this VS 2012 feature)
In my case, I had some Visual Source Safe stuff (my project was created with Visual Studio 2003/2005, yes, very old!)
Once I manually removed the VSS stuff, the conversion succeeded.
PS: I know it's about VS2010, but maybe this helps others.
You can convert a project from VS2010 to VS2012 by doing the following:
Add the 2010 project to your VS2012 solution by right-click on your solution in the Solution Explorer and Select Add --> Existing Project...
The project will appear in the solution and will have (Visual Studio 2010) appended to its name.
Right-click on the added project and select Properties.
In the Configuration Properties --> General pane, change the setting in Platform Toolset field to Visual Studio 2012 (v110)
Repeat for each configuration type, e.g. Release and Debug.
I came across this question while googling for a solution to a specific problem: MSBuild was failing to execute the Publish target against a VS2012 solution that had started life in VS2010 when called from the command line (specifically through TeamCity):
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
MSBuild was looking for the Azure SDK 2.3 targets in the VS10 location (C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets). The cause is explained by Sayed Ibrahim Hashimi in a blog post and, as I understood it, boils down to some decisions they made while enabling cross-version compatibility for solution files. The solution was simple: add the VisualStudioVersion property to the MSBuild invocation, something like this:
msbuild.exe MyAwesomeWeb.sln /p:VisualStudioVersion=11.0
Practically speaking, this overrides the following in each csproj file:
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
Presumably you could get the same result by editing all of these by hand to replace 10.0 with 11.0 but that might break backwards-compatibility -- I haven't tried it. I also haven't tried an update to VS2013 to see if the problem persists.
So to wrap this up by answering the question: yes, there are some differences before you "convert" (using any of the methods offered by other answerers) and some differences remain afterwards.
This is slightly different, but along the same lines so in case it helps anyone:
I was loading a project where it looked like it was loading and then kept showing all projects as unavailable. No errors were on the migration report. I tried reloading the solution and projects many times, using various methods including suggestions here.
Finally I found a "Resolve Errors" option when right clicking on the solution in the Solution Explorer. VS went through a load process again and it worked; no problems.
I don't know what it did differently that time, but apparently it made a difference.
it's to simple just edit the .sol file
change the version to 11
like this
Microsoft Visual Studio Solution File, Format Version 12.00
Visual Studio 2012