I am trying to build a dotnet core web app on a build server that has MsBuild, but not Visual Studio, installed. I cannot get around the message error MSB4236: The SDK 'Microsoft.NET.Sdk.Web' specified could not be found.
The command dotnet --info shows Microsoft.NETCore.App 3.1.0 installed, just as on my development machine where the project builds. The contents of C:\Program Files\dotnet\sdk\3.1.100 appear to match between the two machines. Global.json points to the 3.1.0 version.
Is Microsoft.NET.Sdk.Web a separately-installed thing? I see what look like separate packages, now deprecated, on NuGet, and I'm guessing this is now baked into the base .NET SDK?
Where should I be looking for differences to try to find the missing pieces?
Solved the problem by (1) running vs-buildtools installer to put some additional pieces in place, and (2) adding some NuGet packages for web component.
I'm in need of downgrading from comctl32.ocx v1.4 to v1.3.
I have copied the dll, ocx and oca from a pc with the v1.3.
Unregistered the ocx and registered again but it didn't work v1.4 persists.
If by "1.4 persists" you mean that your project is still trying to use 1.4, this is because it is referenced as 1.4 in the *.vbp file.
if that is the case:
open your project (*.vbp file) with notepad and change the 1.4 to 1.3.
This will make the project use the correct dll version you want it to use. i've had a similar problem with projects that i was working on with a colleague, since our versions of a particular dll are different. Changing this value before opening allows us both to work on it (bit of a hassle but reasons for it). hope it helps.
Basicly I'm super newbie and started internship in IT company. I installed VS with Xamarin. The problem that I'm facing is very frustrating. So even when i create empty project I can't compile it and get error like this :
Severity Code Description Project File Line Suppression State
Warning major version 52 is newer than 51, the highest major version supported by this compiler.
I searched all over google and asked so many people and still no fix of my problem. If anybody can help me via skype or teamwiever i will APPRECIATE so much. My skype: toniterdal , feel free to add me.
I was having the same issue, and tearing my hair out. I had the JDK Version 8 installed, but these warnings wouldn't go away, and eventually they generated a build-breaking error.
When I went to Tools -> Options -> Xamarin, and looked at the Android Settings, the Java Development Kit Location was pointing to jdk.1.7.xxxx, in Program Files (x86).
I changed it to 1.8.0_101, in Program Files. Then I restarted Visual Studio, and the same error happened again. Somehow, Visual Studio was detecting Version 7 of the JDK and pointing it to that automatically.
So the solution turned out to be very simple. As well as installing Version 8 of the JDK, UNINSTALL Version 7 of the JDK. As soon as I did that, Xamarin turned out to be much better behaved. This step solved a whole bunch of seemingly unrelated problems.
That error is telling you that the Java Class version that is being loaded was compiled with Java 8 (52) but Java 7 (51) is trying to load that compiled class.
Java 7 uses major version 51
Java 8 uses major version 52
Check which Java version(s) are installed on your machine and review Xamarin's requirements and Java installation steps (linked below)
Installing the Java SDK (JDK)
For people having problems with setting the appropriate JDK version, you might want to try to override this setting in the vs2015 options dialog:
Delete bin folder and obj folder and run the project it will be work fine
You have a bad proguard.jar file, you need to replace this .jar by a correct version. The steps below describing how to do that. Some colleagues had the same problem here.
Go to Preferences => SDK locations and copy the Android SDK location.
Go to that folder (mostly /Users/USERNAME/Library/Developer/Xamarin/android-sdk-macosx) and go to the folder tools/proguard/lib.
Here you find a proguard.jar.
Rename this to proguard_OLD.jar.
Download the last proguard file (like this one https://sourceforge.net/projects/proguard/files/)
Unzip and place the proguard.jar in the tools/proguard/lib folder
Rebuild your Project
Everything should be fixed!
You can find more info about the bug here:
https://releases.xamarin.com/technical-bulletin-android-sdk-build-tools-24/
For me worked to change the SDK as well, but under Options->Xamarin->Android Settings, I don't have Cross Platform in Options for VS 2015Pro
Note for Windows 64 bit users, the JDK has to be the x86 version not the x64 version.
E.g. C:\Program Files (x86)\Java\jdk1.8.0_111
Kaloyan you can find the setting for the Java SKD under Tools->Options and the click on Xamarin in the Options list, then select Android Settings. I installed the latest Java version (8.0.111) and then did a clean on my project and it runs fine now with no errors. Thank you everyone for your posts!
In my case, i had to reinstall the JDK 8 (the last version) because other versions JDK 7 couldnt work even with new projects or clean up projects, and also i had to do a clean install of the android sdk.
This is how I solved the same issue I faced today:
From Control Panel > Uninstall a Program > uninstall the older Java versions which are on your system.
You should only have Jdk 1.8 and Jre 1.8 on your system.
Now go to C:/Program Files/Java and delete all older java versions.
If you have setup your JDK 1.8 and JRE 8 in C:/Program Files (x86)/Java then cut paste them into C:/Program Files/Java folder.
Then I restarted IntelliJ IDE which I am using. It automatically asked to update the path of SDK. Update the path to point to Jdk 1.8 and then I recompiled my files and things started working well.
Hope it works for you too!
In my case, I had just deleted .class files and worked fine.
I'd like to start playing with the latest versions of Typescript but I have production code using 0.82, and I don't want to switch it until I have checked out the new version (we use lots of modules).
Can multiple versions on a machine play nicely?
This isn't supported in Visual Studio. Best you could do is just install/uninstall on an as-needed basis.
If you just wanted to try compiling things on the command line, you could use the NPM package and download specific versions that way.
Are there any hacks around the normal (and infuriating) Visual Studio Deploy Solution numbering system?
I have many assemblies I'm deploying with a Major.Minor.Build.Revision scheme for assembly versions. When I set the version for the setup.exe/Installer.exe, I can only do Major.Minor.Build. I'm not allow that fourth section for revision. This causes an issue because I key build numbers off date. So if my build is 906 for 09/06/11, I can only install (not uninstall and install, just install) once a day as it will see a previous version with the same version number and say a previous version is blocking install.
Besides using InstallShield (can't use this due to client requirements), are there any hacks to get the normal deploy solution to accept four part versions?
Windows Installer ignores the fourth Product Version field. So as long as you are using MSI packages, there's not much you can do. The old build needs to be manually uninstalled before installing a new build.