got "'dotnet.exe' exited with code -2147450750 " error while running android emulator choose "Release" instead of Debug in visual studio 2022 for MAUI.
How to fix it...
I installed .net latest version
One of our application framework we are using postsharp version 6.3.13 which is supporting us on Visual studio 15 , 17 and 19. Is there any postsharp stable version available which can support for Visual studio 17 , 19 and 22 .
Yes, the last version (PostSharp 6.11) support Visual Studio 2022.4.
##[error]C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1217,5): Error MSB3644: The reference assemblies for .NETFramework,Version=v4.5 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at...
my solution was to upgrade any project targeting .Net Framework 4.5 to 4.7.2 and then building on Visual Studio 2019 instead of 2022, same Win Server 2019
I am also having this issue. Here is my (unsuccessful) progress in trying to solve it
I am also having this issue in Visual Studio 2022 Community after switching all of my solution's projects from various versions of .NET Framework to now all targeting ".NET Framework 4.8".
My error (almost identical to OP's):
C:\Program Files\dotnet\sdk\6.0.101\Microsoft.Common.CurrentVersion.targets(1217,5): error MSB3644: The reference assemblies for .NETFramework,Version=v2.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [C:\Users\MyUsername\source\repos\MyRepo1\Source\Libs\MyLibs\MyLibProject\MyLibProject.csproj]
This error mentions column 5 of line 1217 of file C:\Program Files\dotnet\sdk\6.0.101\Microsoft.Common.CurrentVersion.targets, this leads to the part <GetReferenceAssemblyPaths of the following:
<Target
Name="GetReferenceAssemblyPaths"
DependsOnTargets="$(GetReferenceAssemblyPathsDependsOn);GetFrameworkPaths">
...
<!-- By default if there is no root path set then the task will assume it is Program Files\Reference Assemblies\Microsoft\Framework-->
<GetReferenceAssemblyPaths
Condition="'$(TargetFrameworkMoniker)' != '' and ('$(_TargetFrameworkDirectories)' == '' or '$(_FullFrameworkReferenceAssemblyPaths)' == '')"
TargetFrameworkMoniker="$(TargetFrameworkMoniker)"
RootPath="$(TargetFrameworkRootPath)"
TargetFrameworkFallbackSearchPaths="$(TargetFrameworkFallbackSearchPaths)"
BypassFrameworkInstallChecks="$(BypassFrameworkInstallChecks)"
>
<Output TaskParameter="ReferenceAssemblyPaths" PropertyName="_TargetFrameworkDirectories"/>
<Output TaskParameter="FullFrameworkReferenceAssemblyPaths" PropertyName="_FullFrameworkReferenceAssemblyPaths"/>
<Output TaskParameter="TargetFrameworkMonikerDisplayName" PropertyName="TargetFrameworkMonikerDisplayName" Condition="'$(TargetFrameworkMonikerDisplayName)' == ''"/>
</GetReferenceAssemblyPaths>
...
</Target>
I understand that the parts like $(TargetFrameworkMoniker) are variables. To determine what these evaluate to, I go into Visual Studio, open the csproj file, go to "Build Events > Pre-build event command line" and type echo "TargetFrameworkMoniker" = "$(TargetFrameworkMoniker)". Then I save & build the project, ignore the errors and instead go to the window "Output" to see what these variable evaluate to. I do this for each of the variables. Below is the same code from above, but the variables are now what they actually evaluate to (for me):
<Target
Name="GetReferenceAssemblyPaths"
DependsOnTargets="$(GetReferenceAssemblyPathsDependsOn);GetFrameworkPaths">
...
<!-- By default if there is no root path set then the task will assume it is Program Files\Reference Assemblies\Microsoft\Framework-->
<GetReferenceAssemblyPaths
Condition="'.NETFramework,Version=v4.8' != '' and ('' == '' or '' == '')"
TargetFrameworkMoniker=".NETFramework,Version=v4.8"
RootPath=""
TargetFrameworkFallbackSearchPaths=""
BypassFrameworkInstallChecks=""
>
<Output TaskParameter="ReferenceAssemblyPaths" PropertyName="_TargetFrameworkDirectories"/>
<Output TaskParameter="FullFrameworkReferenceAssemblyPaths" PropertyName="_FullFrameworkReferenceAssemblyPaths"/>
<Output TaskParameter="TargetFrameworkMonikerDisplayName" PropertyName="TargetFrameworkMonikerDisplayName" Condition="'' == ''"/>
</GetReferenceAssemblyPaths>
...
</Target>
I don't see anything that suggests anything other than ".NET Framework 4.8", so I am now unsure how to proceed.
I got this issue resolved by downgrading from Visual Studio 2022 to Visual Studio 2014. I uninstalled Visual Studio 2022 and installed Visual Studio 2014, and the rest fell in place. My installation is now up and running.
Changing from
vmImage: 'windows-latest'
to
vmImage: 'windows-2019'
worked for me. It used to work earlier because 2019 was latest, now the latest is 2022 and there is issue with that.
https://github.com/actions/runner-images/issues/5055
I have two machines so far in our organization where I'm getting the side-by-side error when running powershell commands using CMD.exe. We have no issue running this script on all computer models in Win 7. I've tried reinstalling C++ applications to no avail. Any farther help is greatly appreciated.
SxsTrace:
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
AssemblyDirectory = C:\Windows\System32\WindowsPowerShell\v1.0\
Application Config File = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.Config
-----------------
INFO: Parsing Application Config File C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.Config.
ERROR: Line 0: XML Syntax error.
ERROR: Activation Context generation failed.
End Activation Context Generation.
Event Viewer:
Log Name: Application
Source: SideBySide
Date: 5/21/2019 1:31:45 PM
Event ID: 59
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: test.domain.com
Description:
Activation context generation failed for "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe".Error in manifest or policy file "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.Config" on line 0. Invalid Xml syntax.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SideBySide" />
<EventID Qualifiers="49409">59</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-21T17:31:45.000000000Z" />
<EventRecordID>70132</EventRecordID>
<Channel>Application</Channel>
<Computer>test.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</Data>
<Data>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.Config</Data>
<Data>0</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Applications installed:
Name Version
Microsoft Visual C++ 2005 Redistributable (x64) 8.0.59192
Microsoft Visual C++ 2005 Redistributable (x64) 8.0.61000
Microsoft Visual C++ 2005 Redistributable (x64) 8.0.56336
Microsoft Visual C++ 2005 Redistributable 8.0.61001
Microsoft Visual C++ 2015 x86 Additional Runtime - 14.0.24215 14.0.24215
Microsoft Visual C++ 2015 x86 Minimum Runtime - 14.0.24215 14.0.24215
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 9.0.21022
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 9.0.30729
Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.40660 12.0.40660
Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.40660 12.0.40660
Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.40660 12.0.40660
Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.40660 12.0.40660
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 9.0.30729.6161
Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 11.0.61030
Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 11.0.61030
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030 11.0.61030
Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030 11.0.61030
Microsoft Visual C++ 2015 x64 Additional Runtime - 14.0.23026 14.0.23026
Microsoft Visual C++ 2015 x64 Minimum Runtime - 14.0.23026 14.0.23026
For the registry nothing was done. I thought I'd share it to eliminate troubleshooting steps.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86|policy.9.0.microsoft.vc90.crt
This question already has an answer here:
What does single-quoting do in Windows batch files?
(1 answer)
Closed 3 years ago.
When I load developer tools by:
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.9.7
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
and I try to generate build files for my C++ hello world app in CMD by:
cmake -G 'NMake Makefiles'
I get:
CMake Error: Could not create named generator 'NMake
Generators
Visual Studio 16 2019 = Generates Visual Studio 2019 project files.
Use -A option to specify architecture.
* Visual Studio 15 2017 [arch] = Generates Visual Studio 2017 project files.
Optional [arch] can be "Win64" or "ARM".
Visual Studio 14 2015 [arch] = Generates Visual Studio 2015 project files.
Optional [arch] can be "Win64" or "ARM".
Visual Studio 12 2013 [arch] = Generates Visual Studio 2013 project files.
Optional [arch] can be "Win64" or "ARM".
Visual Studio 11 2012 [arch] = Generates Visual Studio 2012 project files.
Optional [arch] can be "Win64" or "ARM".
Visual Studio 10 2010 [arch] = Generates Visual Studio 2010 project files.
Optional [arch] can be "Win64" or "IA64".
Visual Studio 9 2008 [arch] = Generates Visual Studio 2008 project files.
Optional [arch] can be "Win64" or "IA64".
Borland Makefiles = Generates Borland makefiles.
NMake Makefiles = Generates NMake makefiles.
NMake Makefiles JOM = Generates JOM makefiles.
Green Hills MULTI = Generates Green Hills MULTI files
(experimental, work-in-progress).
MSYS Makefiles = Generates MSYS makefiles.
MinGW Makefiles = Generates a make file for use with
mingw32-make.
# etc.
But if I switch to PowerShell by writing powershell in CMD and run the same command:
cmake -G 'NMake Makefiles'
it's working correctly:
-- The C compiler identification is MSVC 19.16.27027.1
-- The CXX compiler identification is MSVC 19.16.27027.1
# etc.
Any idea why cmake is working in PowerShell but not in CMD?
The Windows Command Prompt does not recognize single quotes as quoting characters. You must use double quotes instead.
Change
cmake -G 'NMake Makefiles'
to
cmake -G "NMake Makefiles"
and the problem will disappear.