I'm developing a desktop application in VB 2019. As soon as I upgraded to 2022 it gave me errors. None of the project settings change. Only the VS version.
I get three errors that prevent the form from displaying. They are:
“is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)”
The variable ‘AxMap1’ is either undeclared or was never assigned.
Duplicate component name ‘AxMap1’. Component names must be unique and case-insensitive.
I can just continue developing in VS 2019 for now but that’s not a permanent solution. Any suggestions on what I can do?
Related
I am using MVC app having .net 4.5 and it was working fine in, 4 days back windows 10 update has happened and my IIS setting has gone.
After that i couldn't able to run my MVC app in Visual studio and it starts giving
Could not load file or assembly
'System.EnterpriseServices.Wrapper.dll' or one of its dependencies.
is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
Every time, and don't understand what could be the reason, i searched so many posts, links, solutions are like moving dlls, etc.
Can somebody give my what is the reason and how can solve it
this might help system enterprice services error
Also, it might be worth re-installing the latest updates to Visual Studio as these often get corrupted on operating system updates.
I've been trying to install VS 2015 Enterprise edition on my computer but keep running into an issue. Hunting through SO for the last 24 hours, I've already tried the devenv.exe /ResetUserData & clearing the VS cache fixes, uninstalling enterprise edition and installing professional edition (which still failed for the same reason) and then reinstalling enterprise edition. I've tried deleting the .vs folder before opening the solution, ensuring that the MVC versions in the /Views/ web.config matches the version of the sites web.config (MVC 5.2.3.0).
As of this morning, I've noticed that it only crashes when I try to open a razor view that wasn't created through Visual Studio 2015 (I was using VS 2012 previously, and I'm trying to work on this project in 2015 now that I have a license). I can right-click in the solution explorer to create a brand new view and write anything I want in it with intellisense and save it, and open it back up without any issues.
I get the whole "An exception has occurred, this may be caused by an extension" message and then visual studio restarts if I try to open up a view that was already created through VS 2012.
I've tried looking inside of the log that it provides but I'm a newer developer so I can't really deduce anything from it..I'll attach it if anyone else can make anything of it.
MS VS Enterprise 2015 - Version 14.0.25029.00 Update 2 RC - .NET Framework Version 4.6.01055
I just cleared out the ActivityLog.XML and forced the error to get a fresh set of details - http://pastebin.com/j7RbGJFP
I found the answer in this blog post - https://blogs.msdn.microsoft.com/webdev/2016/01/12/visual-studio-keeps-showing-suggested-extensions/. It has to do with the extensions suggestion - it turns out if you have files not included in your project, you can't view them because of a bug introduced through the extensions suggestion. If you turn that off and include the views in the project, VS won't crash and you'll have intellisense.
I have a MVC 2 project created in Visual Studio 2010 that use MvcSiteMapProvider.dll and works fine. But when loading the project in Visual Studio 2013, everything else work fine except it crashes at
Html.MvcSiteMap().SiteMapPath
The error message is
An exception of type 'MvcSiteMapProvider.MvcSiteMapException' occurred in MvcSiteMapProvider.dll but was not handled in user code
I believe that MvcSiteMapProvider.dll cannot be loaded correctly. I need help on this. Thanks.
Note that there is a separate DLL for each .NET framework version, and I suspect you are targeting the wrong framework. This can happen if you install MvcSiteMapProvider into your project and then change it to a different .NET framework version.
NuGet does not automatically upgrade/downgrade packages to the currently set framework version. This step must be done manually. The best way is to completely uninstall and reinstall the package as per this document. Also be sure to read this before attempting it.
But do note that if you do this NuGet will not remove any files you have changed (like Mvc.sitemap) and then prompt you whether to overwrite them. You should normally say no to each prompt to ensure your custom configuration is not overwritten.
Also note that it is not sufficient to use Assembly Binding Redirection with MvcSiteMapProvider because with each .NET framework version we create a separate build (DLL) that takes advantage of features that are not present in prior versions.
I cannot see the story board in Visual Studio 2013, when I open it it tells me
There was a problem rendering this document.
Also in the errors list I have the following:
The clocks on the Build Host and this Machine are out of Sync. Please make sure they are within 3 minutes (UTC) of each other.
Failed to retrieve SDK status from server Xamarin.iOS Extension.
Also the output from the MAC server log tells me:
Error sending iOS designer payload
What can be wrong here?
I was also having a similar problem where I couldn't open the story board in Visual Studio 2012 or 2013 (I didn't have any errors in my error list, just the error when displaying the designer). My setup is dev work in Windows 7 with Visual Studio 2012/2013 with a Mac acting as a Build Host. I had just updated my Xamarin version from 3.0.54 to version 3.3.47 (it had been a little while) and I had created a little prototype app a couple days ago with no problems, so I figured I had killed something with the update.
In my case, the solution was checking for updates in Xamarin Studio on the Mac, where it found several that needed updated. After installing the updates on the Mac side, I was able to display my story board in both Visual Studio 2012/2013 without issues... so I chalked it up to version mismatch issues between the Build Host and my dev environment in Windows.
I'm attempting to modify a custom Checkin Policy to work against Visual Studio 2013.
At first, I attempted to just add a new section to the manifest for 2013:
<VisualStudio Version="12.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>
and whilst this allowed it to install, it doesn't allow the policy to run (if I go to the policies>>Add section of TFS it's not present, and the policies throws an exception stating that the Policy is not registered).
After much hunting around, I thought perhaps there was an issue with the Policies.pkgdef - The Extension manager in VS2013 shows it as installed, but it's not showing as installed at Pending Changes. However I can't see any issue with it either:
[$RootKey$\TeamFoundation\SourceControl\Checkin Policies]
"VersionOneTFSPolicy"="$PackageFolder$\VersionOneTFSPolicy.dll"
I've opened it and compiled it in 2013, and fixed any reference issues so that it will compile correctly, but it still doesn't seem to like using it.
Does VS2013 manage Custom Checkin policies differently to 2010/2012? From what I can see it should just work with a manifest change and a recompile.
Edit
So I managed to get the custom policy running on VS2013 by upgrading the reference to Microsoft.TeamFoundation.VersionControl.Client from 11 to 12 and upgrading the project to .Net 4.5. However, this now renders the custom policy unusable on VS2012 (and I would assume 2010 too but I haven't tested that yet). Is there a way to have this run on 2010 through to 2013 from a single VSIX?
In the absence of any other solution, I reverted to the tried and tested method of updating the extension and building it as a new package. So simply having a 2012 version and a completely separate 2013 version.
I am trying to solve this as well, and from everything I have found, the only way to get extensions that target all versions is to actually create 3 separate (2010, 2012 and 2013) extensions, and install them using an InstallShield package that has each one as sub-features that get installed in sequence.
Upgrades are then done on each one individually as the VSIX is actually doing the install.
Links that may help you out on this include:
Single extension targeting VS 2012 and VS 2013
How to target an extension in both VS2012 and VS2010