When doing a "dotnet new WinForms" or "dotnet new Wpf", followed by a "dotnet run" (or starting from VS) I get an error code -2147450730 (0x80008096)

Existing applications are also giving the same error, with 009726 the error is the same.
The last version which worked was 009722!

dotnet --info:

.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview-009728
 Commit:    ac9f27d723

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview-009728\

Host (useful for support):
  Version: 3.0.0-preview-27104-01
  Commit:  410cba8501

.NET Core SDKs installed:
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.403 [C:\Program Files\dotnet\sdk]
  2.1.500-preview-009335 [C:\Program Files\dotnet\sdk]
  3.0.100-preview-009728 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 3.0.0-alpha1-10663 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-alpha1-10663 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.DesktopUI.App 3.0.0-alpha-27030-3 [C:\Program Files\dotnet\shared\Microsoft.DesktopUI.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview-27104-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Don't know if it's related to #134, "does not work" can be anything. I think that one is just a version mismatch.

It seems that despite multiple declarations of availability of daily builds of core-sdk it does not happen. Pace of development in coreclr and corefx repos is very high and there are multiple new features and fixes added daily. Unfortunately they do not propagate to core-sdk builds.

As an active community contributor to .NET Core I find it a bit frustrating as it makes daily work on coding and testing more difficult and time consuming than it could be. I would greatly appreciate if mainatainers of core-sdk repo would live up to community contract described publicly everywhere in the repos and docs.

Following the instructions on Prerequisites for .NET Core on Linux I install

• liblttng-ust0
• libcurl3
• libssl1.0.0
• libkrb5-3
• zlib1g
• libicu60
• libunwind8
• libuuid1

Following the links in Install .NET Core for supported Ubuntu and Linux Mint distributions/versions (64 bit) for installing .NET Core SDK 2.0.3 for Ubuntu 18.04 I get to Install .NET Core 2.0 SDK on Linux Ubuntu 17.10. I select 17.10 because it is the closest to 18.04. This ultimately fails with dotnet-runtime-2.0.3 : Depends: libicu57 but it is not installable:

$ wget -q https://packages.microsoft.com/config/ubuntu/17.10/packages-microsoft-prod.deb

$ sudo dpkg -i packages-microsoft-prod.deb
(Reading database ... 185437 files and directories currently installed.)
Preparing to unpack packages-microsoft-prod.deb ...
Unpacking packages-microsoft-prod (1.0-3) over (1.0-3) ...
Setting up packages-microsoft-prod (1.0-3) ...

$ sudo apt-get install apt-transport-https
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apt-transport-https is already the newest version (1.6.3ubuntu0.1).
0 upgraded, 0 newly installed, 0 to remove and 41 not upgraded.

$ sudo apt-get update
Get:1 file:/var/opt/amdgpu-pro-local ./ InRelease
Ign:1 file:/var/opt/amdgpu-pro-local ./ InRelease
Get:2 file:/var/opt/amdgpu-pro-local ./ Release [816 B]
Get:2 file:/var/opt/amdgpu-pro-local ./ Release [816 B]
Get:3 file:/var/opt/amdgpu-pro-local ./ Release.gpg
Ign:3 file:/var/opt/amdgpu-pro-local ./ Release.gpg         
Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:5 https://download.mono-project.com/repo/ubuntu stable-bionic InRelease                                                        
Hit:6 https://download.docker.com/linux/ubuntu bionic InRelease                                                                    
Hit:7 http://dl.google.com/linux/chrome/deb stable Release                                                                         
Get:8 https://packages.microsoft.com/ubuntu/17.10/prod artful InRelease [2,846 B]                                                  
Hit:9 http://us.archive.ubuntu.com/ubuntu bionic InRelease                                                                         
Hit:10 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                                
Hit:12 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease                          
Hit:13 http://ppa.launchpad.net/git-core/ppa/ubuntu bionic InRelease                           
Get:14 https://packages.microsoft.com/ubuntu/17.10/prod artful/main amd64 Packages [28.7 kB]
Hit:15 http://security.ubuntu.com/ubuntu bionic-security InRelease                   
Fetched 31.6 kB in 1s (44.5 kB/s)                   
Reading package lists... Done

$ sudo apt-get install dotnet-sdk-2.0.3
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dotnet-sdk-2.0.3 : Depends: dotnet-runtime-2.0.3 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

$ sudo apt-get install dotnet-runtime-2.0.3
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dotnet-runtime-2.0.3 : Depends: libicu57 but it is not installable
E: Unable to correct problems, you have held broken packages.

2.1 installs fine, but I need 2.0.
The documentation indicates it should work.
Is there a way to install 2.0 on Ubuntu 18.04?

System.Windows.Media.Interactivity.Wpf is very popular in desktop applications, particularly the Behavior feature for UI mixins. I've just ported an application to WPF Core, but had to #ifdef out a couple of bits which used Interaction.Behaviors.

When converting the project to netcoreapp3.0 and keeping the System.Design reference, the compiler doesn't seem to see the reference:

CS0012 The type 'ComponentDesigner' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <!-- ... -->
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Design" />
    <!-- ... -->
    <FrameworkReference Include="Microsoft.DesktopUI" />
  </ItemGroup>

</Project>

How will this work in the future?

(edit) This gets it to build:

    <Reference Include="System.Design" HintPath="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Design.dll" />

But since System.Design is heavily used at runtime, I'm doubtful that the .NET Framework's System.Design will work.

Every SDK version has its own ProductID on windows machines. Which leads to this:

If this is intended, please close this issue :)

If this is not intended you should choose one GUID as Product ID and replace Product Id="*" with it:
https://github.com/dotnet/core-sdk/blob/ae08a294c9d20d0ed8cbab1394d01f6d04c33fc5/packaging/windows/msbuildextensions/msbuildextensions.wxs#L4

I was trying to add configuration in my class library file . Since the appsettings.json was not generated during creation of class library project I added it manually. After building the project I tried to run it but faced the issue that appsettings.json file is not present in the folder.

I am creating a solution which is having one project in ASP.NET Windows Service and the other project is ASP.NET Core Class Library.

What should be the best way to add configurations for the class library?

On ARM64:

ubuntu@pine64:~/test$ dotnet --version
3.0.100-alpha1-009456
ubuntu@pine64:~/test$ ls /usr/share/dotnet/shared/
Microsoft.NETCore.App

On AMD64:

C:\>dotnet --version
3.0.100-alpha1-009456

C:\>dir "\Program Files\dotnet\shared\Microsoft.AspNetCore.App"
 Volume in drive C is Windows
 Volume Serial Number is 384B-0B6E

 Directory of C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App

09/07/2018  11:25 AM    <DIR>          .
09/07/2018  11:25 AM    <DIR>          ..
05/25/2018  03:46 PM    <DIR>          2.1.0
04/25/2018  09:26 AM    <DIR>          2.1.0-rc1-30667
05/04/2018  02:47 PM    <DIR>          2.1.0-rc1-final
07/24/2018  10:49 AM    <DIR>          2.1.1
07/26/2018  12:48 PM    <DIR>          2.1.2
09/07/2018  11:25 AM    <DIR>          3.0.0-alpha1-10062
               0 File(s)              0 bytes
               8 Dir(s)  157,342,289,920 bytes free

I expect to see Microsoft.AspNetCore.App installed.

It's strange every time I run command "docker-compose build" to build my code,always has a name = none, tag = none image 1.8GB with my image docker.
How can I fix it?
Thanks

This is my docker file:

FROM microsoft/dotnet:2.1.3-aspnetcore-runtime AS base
WORKDIR /app
EXPOSE 80

FROM microsoft/dotnet:2.1.401-sdk AS build
WORKDIR /src
COPY OcelotGateWayAPI/OcelotGateWayAPI.csproj OcelotGateWayAPI/
RUN dotnet restore OcelotGateWayAPI/OcelotGateWayAPI.csproj
COPY OcelotGateWayAPI/NuGet.config OcelotGateWayAPI/
COPY . .
WORKDIR /src/OcelotGateWayAPI
RUN dotnet build OcelotGateWayAPI.csproj -c Release -o /app

FROM build AS publish
RUN dotnet publish OcelotGateWayAPI.csproj -c Release -o /app

FROM base AS final
WORKDIR /app
COPY --from=publish /app .
ENTRYPOINT ["dotnet", "OcelotGateWayAPI.dll"]

buildlog.txt

GivenDotNetUsesMSBuild.ItCanNewRestoreBuildRunCleanMSBuildProject currently modifies the created project to target .NET Core 3.0, since the templates aren't updated to target .NET Core 3.0. Once the templates are updated, we should remove this workaround from the test.

The aspnetcore_base_runtime.version file for 3.0 builds still has a 2.2 version number in it. This is causing debian package creation to fail (as the number is used to construct the --ignore-depends parameter to dpkg).

This should be fixed in the next ASP.NET build. For now I'm disabling creating debian packages, which we should re-enable once we insert an ASP.NET build with the fixed base runtime version.

It seems that core-setup repo is staying on top of master branch for major contributing repos: coreclr, corefx. What is the perspective of having truly nightly builds for the core-sdk repo up and running.

hi At the moment, we can only write xaml code and we cant use designer, so Is there any plan to use wpf designer?

In porting our test suite to .NET Core 3.0, I'm seeing a new failure in one of our tests. When trying to call the GetData API on an instance of IDataObject returned from Clipboard.GetDataObject, I get an InvalidOperationException with the following message:

This type has a ComVisible(false) parent in its hierarchy, therefore QueryInterface calls for IDispatch or class interfaces are disallowed

This may be related to issue #149

To reproduce the issue:

• clone the repo https://github.com/nick-beer/IDataObjectBug
• Run the test DataObject_Fails from within the 'Tests' folder

With version 3.0.100-alpha1-009108 of the .NET Core SDK, running dotnet --version gives me 2.2.100-refac-20180613-1.

The version number is probably coming from the assembly info of dotnet.dll, which is built from dotnet/cli. So once we insert a version with the updated branding into dotnet/toolset and insert that into dotnet/core-sdk, then it would probably show a 3.0 version... but it will still be the wrong 3.0 version. The version displayed should be the version of core-sdk, not the version of cli or toolset.

There is a .version file dropped in the sdk folder. Currently it looks like this has the hash and the version of the toolset build. We should modify the process so that this .version file is dropped by the core-sdk build and includes the core-sdk version and hash. Then we should modify the code from dotnet --version to read this file to get the version number.

We could also consider having multiple .version files if we think it's valuable to preserve the version and hash info of the toolset repo.

I built a proof of concept for sharing code between Desktop and Core versions of WPF:

The repository is at https://github.com/gulbanana/wpf-multitarget. It works well enough to be very encouraging; here are some gotchas I ran into along the way.

• The SDK doesn't contain a glob for Page items, nor does it nest them using DependentUpon.

• Building in visual studio sometimes takes a couple of tries. in particular the first clean rebuild seems to fail. This seems related to the generated xaml project.

• When importing the props and targets, netfx must not use Microsoft.NET.Sdk.Wpf, because it already has winfx.targets coming from Microsoft.NET.Sdk. However, corefx needs the WPF targets imported after the core sdk targets. this means we can't use Project Sdk= but must instead decompose the sdk into hand-written imports.

• Error messages are poor; in particular, failures to load xaml will be reported at runtime as a ArgumentNullException failing to format an error. Here's an incomprehensible stack trace which really meant "you have failed to declare an xmlns in a resource dictionary":
  

• dotnet build cannot be used yet, presumably due to the dependency on Microsoft.WinFX.targets. I'm sure this one is a known issue, but it's irritating... yet useful for multi-targetting compatibility. Can we make sure that multitargeting remains possible when this is somehow fixed? :)

• The lack of a Properties.cs in .net core projects - for the most part a good thing - means that there's no obvious place to put the ThemeInfo attribute required for control xaml discovery.

• You basically have to be a WPF expert to discover most of this. Sharing code between legacy netfx and new corefx apps is going to be a major use case, so it could really use templates and polish. At the moment, if you fall slightly off the interop path then you get upsettting msbuild errors ("required targets are missing" and everything unloads itself) or upsetting runtime errors ("load failure in something xaml did somewhere").

Success info for latest DotNet Core SDK v2.1.302 for x86 Windows installer points to wrong installation location:

Information points to \Program Files\dotnet while it should be \Program Files (x86)\dotnet

I'm referencing DevExpress's NuGet packages which target net40 in a netcoreapp3.0 project using <FrameworkReference Include="Microsoft.DesktopUI" />. NuGet gives a warning but everything should restore fine. From BUILD and dotnetconf, the expectation is that many .NET Framework assemblies actually do just work for the time being.

However, the compiler isn't referencing any assemblies from the package dependencies of these packages. In order to get the compiler to see assemblies in the package graph, I have to directly reference every package in the tree.

These packages come from a private feed with DevExpress customer API token in the URL, but there's nothing unusual about them.

Here's the workaround for now:

  <ItemGroup>
    <!-- ... -->
    <PackageReference Include="DevExpress.Win.Reporting" Version="17.2.4" />
    <PackageReference Include="DevExpress.Win.SpellChecker" Version="17.2.4" />
    <!-- ... -->
  </ItemGroup>

  <ItemGroup Label="Workaround for broken transitive restore (https://github.com/dotnet/core-sdk/issues/78)">
    <!-- Direct dependency of both DevExpress.Win.Reporting and DevExpress.Win.SpellChecker -->
    <PackageReference Include="DevExpress.Win" Version="17.2.4" />
    <!-- Direct dependencies of DevExpress.Win.Reporting -->
    <PackageReference Include="DevExpress.Win.Charts" Version="17.2.4" />
    <PackageReference Include="DevExpress.Reporting.Core" Version="17.2.4" />
    <PackageReference Include="DevExpress.Utils.UI" Version="17.2.4" />
    <!-- Direct dependency of DevExpress.Win.Reporting, DevExpress.Win.Charts, and DevExpress.Reporting.Core -->
    <PackageReference Include="DevExpress.Charts" Version="17.2.4" />
      <!-- Direct dependency of DevExpress.Win.Reporting, DevExpress.Win.Charts, and DevExpress.Charts -->
    <PackageReference Include="DevExpress.Charts.Core" Version="17.2.4" />
    <!-- Direct dependency of DevExpress.Win.Reporting and DevExpress.Utils.UI -->
    <PackageReference Include="DevExpress.Win.RichEdit" Version="17.2.4" />
    <!-- Direct dependencies of DevExpress.Win, DevExpress.Win.Reporting, and DevExpress.Reporting.Core -->
    <PackageReference Include="DevExpress.PivotGrid.Core" Version="17.2.4" />
    <PackageReference Include="DevExpress.RichEdit.Core" Version="17.2.4" />
    <!-- Direct dependencies of many of the above -->
    <PackageReference Include="DevExpress.Data" Version="17.2.4" />
    <PackageReference Include="DevExpress.Utils" Version="17.2.4" />
  </ItemGroup>

In #14 the links were removed

@livarcocc I can see the "coming soon" text, I created the issue to keep track of it.

It is blocking dotnet/corefx#30703

Description

dotnet build or dotnet run fails when the project is in a folder that contains the literal %20 in the name.

running dotnet build returns

C:\Program Files\dotnet\sdk\2.1.401\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(198,5): 
error NETSDK1004: Assets file 'C:\test test\obj\project.assets.json' not found. 
Run a NuGet package restore to generate this file. [C:\test%20test\testtest.csproj]

The build failed. Please fix the build errors and run again.

Please note that the folder is named test%20test (not with an actual space) and that the file not found says folder "test test" with an actual space
I'm running dotnet version 2.1.401 on windows 10

Repo

in a command window do

mkdir test%20test
cd test%20test
dotnet new console
dotnet run

Expected

Hello World! 

Actual Result

C:\Program Files\dotnet\sdk\2.1.401\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(198,5): 
error NETSDK1004: Assets file 'C:\test test\obj\project.assets.json' not found. 
Run a NuGet package restore to generate this file. [C:\test%20test\testtest.csproj]

The build failed. Please fix the build errors and run again.

linux subsystem has the same issue:
output for dotnet run in de ubuntu shell

/usr/share/dotnet/sdk/2.1.401/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(198,5):
 error NETSDK1004: Assets file '/mnt/c/test test/obj/project.assets.json' not found. 
Run a NuGet package restore to generate this file. [/mnt/c/test%20test/testtest.csproj]

The build failed. Please fix the build errors and run again.

extra info

dotnet --info output:

.NET Core SDK (reflecting any global.json):
 Version:   2.1.401
 Commit:    91b1c13032

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.401\

Host (useful for support):
  Version: 2.1.3-servicing-26724-03
  Commit:  124038c13e

.NET Core SDKs installed:
  2.0.2 [C:\Program Files\dotnet\sdk]
  2.1.201 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.300-preview2-008533 [C:\Program Files\dotnet\sdk]
  2.1.300 [C:\Program Files\dotnet\sdk]
  2.1.401 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-preview2-26406-04 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.3-servicing-26724-03 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Currently it's a manual process to merge changes from the sdk, cli, and toolset repos into core-sdk. We should set up maestro so that these insertions will be automatically generated.

FYI @livarcocc

dotnet new WPF
open project in VS2017 preview
Build and run app works fine
Publish, change profile to self-contained
double click the exe. app crashes without seeing any UI

Application Error 1000
Faulting application name: netcorewpf.exe, version: 0.0.0.0, time stamp: 0x5ba8632c
Faulting module name: KERNELBASE.dll, version: 10.0.17763.1, time stamp: 0x30bd5043
Exception code: 0xe0434352
Fault offset: 0x0011aaf2
Faulting process id: 0x3e88
Faulting application start time: 0x01d45523c916af67
Faulting application path: C:\scratch\netcorewpf\bin\Release\netcoreapp3.0\win-x86\netcorewpf.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: e86dcdad-6d14-4469-91e2-64ecb2712fca
Faulting package full name:
Faulting package-relative application ID:

.NET Runtime 1026
Application: netcorewpf.exe
CoreCLR Version: 4.6.26921.6
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException: The type initializer for 'System.Windows.Window' threw an exception. ---> System.InvalidProgramException: Failed WPF DLL consistency checks. Expected location: C:\Users\mahoekst.nuget\packages\runtime.win-x86.microsoft.desktopui.app\3.0.0-alpha-26921-3\runtimes\win-x86\lib\netcoreapp3.0.
DLL Name: PresentationNative_cor3.dll DLL Location: C:\Users\mahoekst.nuget\packages\runtime.win-x86.microsoft.desktopui.app\3.0.0-alpha-26921-3\runtimes\win-x86\native

at System.Windows.WpfDllVerifier.VerifyWpfDllSet(String[] additionalDlls) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\WpfDllVerifier.cs:line 117
at System.Windows.Window..cctor() in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Window.cs:line 121
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Markup\XamlReader.cs:line 416
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Markup\WpfXamlLoader.cs:line 154
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Markup\WpfXamlLoader.cs:line 39
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Markup\XamlReader.cs:line 981
at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 666
at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 614
at System.Windows.Application.DoStartup() in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 1678
at System.Windows.Application.<.ctor>b__1_0(Object unused) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 201
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) in E:\A_work\160\s\src\WPF\src\WindowsBase\MS\Internal\Threading\ExceptionWrapper.cs:line 104
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) in E:\A_work\160\s\src\WPF\src\WindowsBase\MS\Internal\Threading\ExceptionWrapper.cs:line 37
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 3121
at System.Windows.Threading.DispatcherOperation.InvokeImpl() in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\DispatcherOperation.cs:line 583
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\DispatcherOperation.cs:line 527
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj) in E:\A_work\160\s\src\WPF\src\Shared\MS\Internal\CulturePreservingExecutionContext.cs:line 234
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state) in E:\A_work\160\s\src\WPF\src\Shared\MS\Internal\CulturePreservingExecutionContext.cs:line 185
at System.Windows.Threading.DispatcherOperation.Invoke() in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\DispatcherOperation.cs:line 438
at System.Windows.Threading.Dispatcher.ProcessQueue() in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 2271
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 2509
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) in E:\A_work\160\s\src\WPF\src\Shared\MS\Win32\HwndWrapper.cs:line 345
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) in E:\A_work\160\s\src\WPF\src\Shared\MS\Win32\HwndSubclass.cs:line 494
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) in E:\A_work\160\s\src\WPF\src\WindowsBase\MS\Internal\Threading\ExceptionWrapper.cs:line 104
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) in E:\A_work\160\s\src\WPF\src\WindowsBase\MS\Internal\Threading\ExceptionWrapper.cs:line 37
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 3121
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 1449
at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 1161
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) in E:\A_work\160\s\src\WPF\src\Shared\MS\Win32\HwndSubclass.cs:line 392
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(MSG& msg) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 2482
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 2332
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame) in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 370
at System.Windows.Threading.Dispatcher.Run() in E:\A_work\160\s\src\WPF\src\WindowsBase\System\Windows\Threading\Dispatcher.cs:line 329
at System.Windows.Application.RunDispatcher(Object ignore) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 2782
at System.Windows.Application.RunInternal(Window window) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 1858
at System.Windows.Application.Run(Window window) in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 269
at System.Windows.Application.Run() in E:\A_work\160\s\src\WPF\src\PresentationFramework\System\Windows\Application.cs:line 231
at netcorewpf.App.Main()

The "Installation note" section in the .NET Core SDK installer is probably not applicable to .NET Core 3.0. It should be removed or updated.

I was looking to see how I can incorporate the MSBuild.Sdk.Extras with the new WindowsDesktop SDK and hit a few challenges. The overall scenario is getting multi-targeting to work, where iOS, UWP, Android, Tizen, are handled by the Extras, while WPF/WinForms is handled by the WindowsDesktop SDK.

Here’s where I hit some issues (numbered for reference):

1. The Microsoft.NET.Sdk props do not define a base directory or a version. I need a hack to see if WindowsDesktop is available like this: https://github.com/onovotny/MSBuildSdkExtras/blob/master/Source/MSBuild.Sdk.Extras/Sdk/Sdk.props#L16-L17
2. Once calculated, the WindowsDesktop\targets\props (sorry, no public source, need to refer to files in the sdk dir), has a FrameworkReference for Microsoft.WindowsDesktop.App without a condition on UseWPF/UseWindowsForms. It applies to any .NET Core App, but someone using the extras may not want that desktop app for their .NET Core App target. I need a way to turn that implicit reference off. Can there be a new property it checks (like IsDesktopProject or ProjectType = Desktop) to “light up” that stuff? The other item groups are keyed off of either UseWpf or UseWindowsForms, so they’re okay. I have a temporary workaround here, but this seems hacky. Need to know when to bring it in discreetly: https://github.com/onovotny/MSBuildSdkExtras/blob/master/Source/MSBuild.Sdk.Extras/Sdk/Sdk.props#L29
3. In WindowsDesktop\targets\targets, The import for the WinFX targets has the same issue as the FrameworkReference. I need a way to conditionally import those (or turn that off unless the ProjectType = Desktop)…something. The other ItemGroup and Target are conditioned on UseWPF, so that’s okay too. I worked around this, for now, by essentially keying off of UseWPF since all the items/targets/imports were tied to it. https://github.com/onovotny/MSBuildSdkExtras/blob/master/Source/MSBuild.Sdk.Extras/Sdk/Sdk.targets#L17. This could be brittle though, especially if other things get added. Essentially need a way to turn pieces on/off as needed (like the WinFX imports).

I think that should cover it? If a couple of conditionals are added, I can have people use the MSBuild.Sdk.Extras as the SDK and pull in the WindowsDestop props/targets. The TFM-specific conditions would add all the items/targets.

What scenarios are covered by the Microsoft.WindowsDesktop.App FrameworkReference where neither UseWpf nor UseWindowsForms would be defined?

--

Overall, I wound up having to bypass the WindowsDesktop SDK itself and go straight to its targets, since I couldn't compose things the way I needed to in the right order. I'm hoping for ideas/suggestions/improvements going forward.

@leandro-fernandez commented on Thu Jul 26 2018

Self-contained publish failing in .net core sdk 2.1.302 with error NU1605 : Detected package downgrade: Microsoft.NETCore.App from 2.1.2 to 2.1.0

Description

After I migrated from .netcoreapp2.0 to .netcoreapp2.1, I am getting a error NU1605: Detected package downgrade: Microsoft.NETCore.App from 2.1.2 to 2.1.0 when running dotnet publish with the -r option.

snapshot

one of my class libs csproj

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup Label="Globals">
    <SccProjectName>SAK</SccProjectName>
    <SccProvider>SAK</SccProvider>
    <SccAuxPath>SAK</SccAuxPath>
    <SccLocalPath>SAK</SccLocalPath>
  </PropertyGroup>
  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <DebugType>full</DebugType>
    <DebugSymbols>true</DebugSymbols>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.2" />
    <PackageReference Include="Microsoft.AspNetCore.TestHost" Version="2.1.1" />
    <PackageReference Include="xunit" Version="2.4.0" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\Rubicon.ReverseProxy\Rubicon.ReverseProxy.csproj" />
  </ItemGroup>
</Project>

main project csproj

<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup Label="Globals">
    <SccProjectName>SAK</SccProjectName>
    <SccProvider>SAK</SccProvider>
    <SccAuxPath>SAK</SccAuxPath>
    <SccLocalPath>SAK</SccLocalPath>
  </PropertyGroup>

  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
    <OutputType>Exe</OutputType>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <DebugType>full</DebugType>
    <DebugSymbols>true</DebugSymbols>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.2" />
    <PackageReference Include="Polly" Version="6.1.0" />
    <PackageReference Include="Serilog.AspNetCore" Version="2.1.1" />
    <PackageReference Include="Serilog.Sinks.Console" Version="3.1.1" />
    <PackageReference Include="Steeltoe.CloudFoundry.ConnectorCore" Version="2.0.0" />
    <PackageReference Include="Steeltoe.Management.CloudFoundryCore" Version="2.0.1" />
  </ItemGroup>
  <ItemGroup>
    <None Update="deploy.*.bat">
      <DependentUpon>deploy.bat</DependentUpon>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </None>
    <None Update="manifest.*.yml">
      <DependentUpon>manifest.yml</DependentUpon>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </None>
  </ItemGroup>
  <ItemGroup>
    <None Update="manifest.yml">
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </None>
  </ItemGroup>
  <ProjectExtensions><VisualStudio><UserProperties appsettings_1json__JSONSchema="" /></VisualStudio></ProjectExtensions>

</Project>

@joshfree commented on Fri Jul 27 2018

@weshaggard

@Petermarcu commented on Fri Jul 27 2018

One of the packages you are referencing is likely pulling in a lower version of a package. @DamianEdwards have you seen this?

@weshaggard commented on Fri Jul 27 2018

Based on the error screenshot it looks like a couple of your test projects are directly referencing 2.1.0 of the runtime either via a direct PackageReference or via overriding the RuntimeFrameworkVersion. Can you provide a pointer to your Rubicon.ReversProxy.Tests.Common.csproj?

@leandro-fernandez commented on Thu Aug 02 2018

The weird part is that running dotnet publish without -r (i.e., to output a dll) doesn't cause any issues.
Here's the Rubicon.ReverseProxy.Tests.Common.csproj.

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup Label="Globals">
    <SccProjectName>SAK</SccProjectName>
    <SccProvider>SAK</SccProvider>
    <SccAuxPath>SAK</SccAuxPath>
    <SccLocalPath>SAK</SccLocalPath>
  </PropertyGroup>

  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
    <RuntimeIdentifier>win10-x64</RuntimeIdentifier>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <DebugType>full</DebugType>
    <DebugSymbols>true</DebugSymbols>
    <NoWarn>$(NoWarn);NU1605</NoWarn>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.TestHost" Version="2.0.2" />
    <PackageReference Include="xunit" Version="2.3.1" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\Rubicon.ReverseProxy\Rubicon.ReverseProxy.csproj" />
  </ItemGroup>

</Project>

@leandro-fernandez commented on Thu Aug 02 2018

By the way, I added the <NoWarn>$(NoWarn);NU1605</NoWarn> as a workaround for this issue. If I remove if, I get the error messages. But it doesn't look like a good idea to simply suppress these errors.

@DamianEdwards commented on Thu Aug 02 2018

Have you tried updating your reference to Microsoft.AspNetCore.TestHost to the latest version?

@leandro-fernandez commented on Thu Aug 02 2018

I have. Doesn't make a difference with regards to the NU1605 : Detected package downgrade error.
I left it as 2.0.2 in the end because the latest version of Microsoft.AspNetCore.TestHost changed its behavior somehow and it broke our tests.

@dasMulli commented on Thu Aug 02 2018

In your test project, try setting

<PropertyGroup>
  <TargetLatestRuntimePatch>true</TargetLatestRuntimePatch>
</PropertyGroup>

in the test project.

This is likely caused by NuGet using different properties to restore than the actual build will use - the RuntimeIdentifier will not be forward across P2P references during the build but NuGet will evaluate all projects using the global property and thus the runtime roll-forward kicks in.

Also see dotnet/sdk#1834

@dasMulli commented on Thu Aug 02 2018

And btw roll-forward doesn't kick in for test projects since they are libraries by default and the test SDK changes them to <OutputType>Exe</OutputType> too late for the self-contained roll-forward IIRC.

In theory, you can also work around this by setting <OutputType>Exe</OutputType> in the test project instead of the TargetLatestRuntimePatch mentioned above.

@jkruer01 commented on Thu Aug 16 2018

I have the same issue. Builds locally fine, but throws same error as above for my test project on the build server.

@jkruer01 commented on Thu Aug 16 2018

Adding <OutputType>Exe</OutputType> worked for me.

@duncanawoods commented on Thu Aug 16 2018

Adding just <OutputType>Exe</OutputType> got over the downgrade error but publish then failed on:

NETSDK1061: The project was restored using Microsoft.NETCore.App version 2.1.2, but with current settings, version 2.1.0 would be used instead

Adding <TargetLatestRuntimePatch>true</TargetLatestRuntimePatch> fixes it fully.

@WhitWaldo commented on Thu Aug 16 2018

My unit test project showed up as running 2.1.0 where all the other projects in my solution were running 2.1.2 and I got the same error.

Adding <PropertyGroup><TargetLatestRuntimePatch>true</TargetLatestRuntimePatch></PropertyGroup> solved the issue for me as well.

@ramoneeza commented on Fri Aug 17 2018

Change .csproj doesn't work.

Nuget problems are persistent with any .net core 2.1 project I start.

When I use "Nuget Console" with "Update-Package -reinstall", then Project name is cleared and it displays "'default' project not found" error. :-(

My visual studio has several Nuget related errors and repair/reinstall doesn't fix anything.

For some reason this catches the eye and looks unfinished. I think if there was a preceding sentence, it might be OK.

This repo is no longer generating the msbuildextensions, but it does generate the msi for it. We need to turn it back on, but only after we have the toolset (or the CLI) produce the appropriate msbuildextension artifact to be consumed here.

In porting our test suite to .NET Core 3.0, I'm seeing a new failure in one of our tests. Code running as the result of a call to InvokeAsync/BeginInvoke should have a DispatcherSynchronization context whose internal priority matches that of the call to BeginInvoke/InvokeAsync. This was true under .NET Framework, but is no longer true under .NET Core 3. The synchronization context always has a priority of DispatcherPriority.Normal - regardless of the priority given to BeginInvoke/InvokeAsync.

This is important to our application because it is very sensitive to priority, and we often have side effect work that runs as a result of various calls to BeginInvoke. If this side effect work ends up in async/await code paths, the sync context that is captured will have the wrong, undesired priority.

To reproduce the issue:

• clone the repo https://github.com/nick-beer/SyncCxtPriorityBug
• Run the test SyncContextPriority_Fails in the Tests folder.

@bmeverett commented on Wed Feb 21 2018

I have a class library that needs to be signed due to other references in the project it is in. I tried to pull it into my Mac app using Xamarin and Visual Studio for Mac but I keep getting this error:

Target ResolveAssemblyReferences:
    A TargetFramework profile exclusion list will be generated.
Target ResolveKeySource:
    /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018: The "ResolveKeySource" task failed unexpectedly.
    /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018: System.NotSupportedException: Specified method is not supported.
    /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018:   at System.Runtime.InteropServices.RuntimeEnvironment.GetRuntimeInterfaceAsObject (System.Guid clsid, System.Guid riid) [0x00006] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/referencesource/mscorlib/system/runtime/interopservices/runtimeenvironment.cs:204 
    /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018:   at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
    /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018:   at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00032] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.Reflection/MonoMethod.cs:305 
Done building target "ResolveKeySource" in project "POSModel.Shared.csproj" -- FAILED.

Done building project "POSModel.Shared.csproj" -- FAILED.

Build FAILED.

/Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018: The "ResolveKeySource" task failed unexpectedly.
/Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018: System.NotSupportedException: Specified method is not supported.
/Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018:   at System.Runtime.InteropServices.RuntimeEnvironment.GetRuntimeInterfaceAsObject (System.Guid clsid, System.Guid riid) [0x00006] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/referencesource/mscorlib/system/runtime/interopservices/runtimeenvironment.cs:204 
/Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018:   at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
/Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(3105,5): error MSB4018:   at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00032] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.Reflection/MonoMethod.cs:305 
    0 Warning(s)
    1 Error(s)

It obviously says NotSupported, but didn't know if there was any way to sign this on the Mac or any plans to support this in the future. I tried to do a search through issues and couldn't find anything related.

I noticed the strong name tool does work on Mac sn -i key.pfx <machine container>. However because of the NotSupported exception I am not given a machine container to sign against.

Any help would be appreciated!

I installed SDK 3.0.100.009456 from https://dotnetcli.blob.core.windows.net/dotnet/Sdk/master/dotnet-sdk-latest-win-x64.exe.

When I open a netcoreapp3.0 exe or library project in Visual Studio 15.8.4, it shows this message:

There's no way it's newer than .NET Core 3.0.

Projects look similar to:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <!-- ... -->
  </PropertyGroup>

  <ItemGroup>
    <!-- ... -->
    <FrameworkReference Include="Microsoft.DesktopUI" />
  </ItemGroup>

</Project>

Steps to reproduce

Execute Installer on a Windows machine with a high resolution and dpi scaling turned on.
In my case 1080p and 125% scaling.

Expected behavior

Clean interface with sharp font

Actual behavior

very blurry fonts during installation

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
Version: 1.0.1
Commit SHA-1 hash: 005db40

Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.0.1

I install the dotnet sdk 3.0.100 on Windows Server 2019 (Hyper-V)
It won't work on Window Server 2019, but I will work after I dotnet publish --r win-x64 -c release and copy the output to windows 10 ,

PS C:\Users\Administrator\Documents\WPFCore> dotnet --info
.NET Core SDK（反映任何 global.json）:
 Version:   3.0.100-preview-009756
 Commit:    4e29d9d96f

运行时环境:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview-009756\

Host (useful for support):
  Version: 3.0.0-preview-27114-01
  Commit:  3fd6793563

.NET Core SDKs installed:
  3.0.100-preview-009756 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 3.0.0-alpha1-10663 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 3.0.0-alpha1-10663 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.0-preview-27114-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-alpha-27115-10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Some of the installation files are too big to download for those with low internet speeds, a web installer and a modular installer (allows the user to choose which components to download & install) should help.

Cause i had problems with 2.1.302 sdk i wanted to downgrade to 2.1.301
After uninstalling that SDK my Visual Studio 2017 project wouldn't load and show "Project file is incomplete. Expected imports are missing"

Solution was to remove C:\Program Files\dotnet\sdk\2.1.302 folder (which was already empty cause of uninstall)

Uninstaller should delete that automatically!

Reference: #31

Typically the SDK-version directory under the SDK directory [toolset] matches the advertised SDK version.

How is the dotnet/Toolset version to be used?

From @Eilon on July 18, 2018 22:40

Steps to reproduce

Install latest .NET Core SDK for Windows installer from: https://www.microsoft.com/net/download/windows
I used https://www.microsoft.com/net/download/thank-you/dotnet-sdk-2.1.302-windows-x64-installer

Note: I'm not sure if this is the right repo because I couldn't find these URLs specified in the code here.

Expected behavior

ARP entries should use HTTPS URLs to https://dotnet.github.io/ (or perhaps they should really link to https://dot.net/ or https://www.microsoft.com/net).

Actual behavior

HTTP URLs are used:

Environment data

N/A

Copied from original issue: dotnet/core-setup#4379

Was expecting netcoreapp3.0

Workaround -- Update project file to the following:

<TargetFramework>netcoreapp3.0</TargetFramework>

the latest version of the sdk breaks our web.config.

this is our template:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <system.webServer>
        <handlers>
            <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
        </handlers>
        <aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" startupTimeLimit="3600" requestTimeout="23:00:00" />
    </system.webServer>
    <location path="some path">
        <system.web>
            <httpRuntime maxRequestLength="614400" />
        </system.web>
        <system.webServer>
            <security>
                <requestFiltering>
                    <!-- default is 30.000.000 or approx. 28,6102 Mb-->
                    <requestLimits maxAllowedContentLength="629145600" />
                </requestFiltering>
            </security>
        </system.webServer>
    </location>
</configuration>

version 2.1.302 of the sdk creates the following web.config, which is correct:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <system.webServer>
        <handlers>
            <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
        </handlers>
        <aspNetCore processPath=".\OurAppName.exe" arguments="" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" startupTimeLimit="3600" requestTimeout="23:00:00" />
    </system.webServer>
    <location path="some path">
        <system.web>
            <httpRuntime maxRequestLength="614400" />
        </system.web>
        <system.webServer>
            <security>
                <requestFiltering>
                    <!-- default is 30.000.000 or approx. 28,6102 Mb-->
                    <requestLimits maxAllowedContentLength="629145600" />
                </requestFiltering>
            </security>
        </system.webServer>
    </location>
</configuration>

version 2.1.400 creates the following web.config, which IIS does not like very much for obvious reasons:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <system.webServer>
        <handlers>
            <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
        </handlers>
        <aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" startupTimeLimit="3600" requestTimeout="23:00:00" />
    </system.webServer>
    <location path="some path">
        <system.web>
            <httpRuntime maxRequestLength="614400" />
        </system.web>
        <system.webServer>
            <security>
                <requestFiltering>
                    <!-- default is 30.000.000 or approx. 28,6102 Mb-->
                    <requestLimits maxAllowedContentLength="629145600" />
                </requestFiltering>
            </security>
            <handlers>
                <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
            </handlers>
            <aspNetCore processPath=".\OurAppName.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
        </system.webServer>
    </location>
</configuration>

I can't install the daily builds for the master (3.0) branch because of a missing dependency: aspnetcore-runtime-3.0. Is it really a dependency? If yes, where can it be found?

I found the other dependency (dotnet-runtime-3.0) there: https://github.com/dotnet/core-setup#daily-builds.

# dpkg -i dotnet-sdk-latest-x64.deb 
Selecting previously unselected package dotnet-sdk-3.0.
(Reading database ... 441980 files and directories currently installed.)
Preparing to unpack dotnet-sdk-latest-x64.deb ...
Unpacking dotnet-sdk-3.0 (3.0.100-alpha1-009410-1) ...
dpkg: dependency problems prevent configuration of dotnet-sdk-3.0:
 dotnet-sdk-3.0 depends on aspnetcore-runtime-3.0 (>= 3.0.0~alpha1-10062); however:
  Package aspnetcore-runtime-3.0 is not installed.

dpkg: error processing package dotnet-sdk-3.0 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 dotnet-sdk-3.0

# apt install aspnetcore-runtime-3.0
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package aspnetcore-runtime-3.0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'aspnetcore-runtime-3.0' has no installation candidate

We turned off crossgen because our toolset is already crossgened. Once we start producing a portable toolset, we need to re-enable crossgen.

I'm disabling the GivenAspNetAppsResolveImplicitVersions tests for .NET Core 3.0, as they don't currently work for 3.0, we are disabling the ASP.NET implicit versions for 2.x (dotnet/aspnetcore#3292), and for 3.0 we will be changing how this works.

Once we have an implementation for how Shared Frameworks will work in 3.0, we should re-add tests as appropriate to make sure any hard-coded versions are kept up to date.

dotnet --version = 3.0.100-preview-009756
hi i want run my wpf app on linux so:
1 - Create WPF app dotnet new wpf
2 - dotnet publish -c release -r ubuntu.16.04-x64
3 - Copy Publish folder on linux
4 - chmod 777 ./wpfapp
5 - ./wpfapp
but i get this error:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.

The message in the .NET Core 3.0 installer still shows for .NET Core 2.2, it needs to be updated for 3.0.

Screen:

Currently, the toolset (sdk/version_number) is being placed under the toolset's version number. We need to update our build to move the toolset under a folder versioned with the core-sdk version. We will also need to set/update the .version file with the appropriate version.

This is a continuation of #93, which was closed for some reason.

As mentioned in that post

2.1 installs fine, but I need 2.0.

I need 2.0 because there is a problem with the Akka.net/dotnetty combination for clustering on 2.1 that does not occur in 2.0.

Is there a way to install 2.0 on Ubuntu 18.04? The documentation indicates it should work. I am not interested in new distributions, just the distributions documented.

We don't currently have builds of WindowsDesktop for arm, I am not even sure if that makes sense. For the win-arm builds, we simply disabled carrying that runtime.

We are working on porting a WPF application and we are seeing a lot of InvalidOperationExceptions being thrown and usually handled when performing actions like opening menus.

Here is the exception information:

System.InvalidOperationException
HResult=0x80131509
Message=This type has a ComVisible(false) parent in its hierarchy, therefore QueryInterface calls for IDispatch or class interfaces are disallowed.
Source=
StackTrace:

And here is a typical call stack:
[Native to Managed Transition]
[Managed to Native Transition]
UIAutomationProvider.dll!System.Windows.Automation.Provider.AutomationInteropProvider.RaiseAutomationPropertyChangedEvent(System.Windows.Automation.Provider.IRawElementProviderSimple element, System.Windows.Automation.AutomationPropertyChangedEventArgs e) Unknown
PresentationCore.dll!System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree() Unknown
PresentationCore.dll!System.Windows.Automation.Peers.AutomationPeer.FireAutomationEvents() Unknown
PresentationCore.dll!System.Windows.ContextLayoutManager.fireAutomationEvents() Unknown
PresentationCore.dll!System.Windows.ContextLayoutManager.UpdateLayout() Unknown
PresentationCore.dll!System.Windows.ContextLayoutManager.UpdateLayoutCallback(object arg) Unknown
PresentationCore.dll!System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork() Unknown
PresentationCore.dll!System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() Unknown
PresentationCore.dll!System.Windows.Media.MediaContext.RenderMessageHandlerCore(object resizedCompositionTarget) Unknown
PresentationCore.dll!System.Windows.Media.MediaContext.RenderMessageHandler(object resizedCompositionTarget) Unknown
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) Unknown
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source, System.Delegate callback, object args, int numArgs, System.Delegate catchHandler) Unknown
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeImpl() Unknown
WindowsBase.dll!MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(object obj) Unknown

System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Line 168 C#
WindowsBase.dll!MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.Invoke() Unknown
WindowsBase.dll!System.Windows.Threading.Dispatcher.ProcessQueue() Unknown
WindowsBase.dll!System.Windows.Threading.Dispatcher.WndProcHook(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) Unknown
WindowsBase.dll!MS.Win32.HwndWrapper.WndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) Unknown
WindowsBase.dll!MS.Win32.HwndSubclass.DispatcherCallbackOperation(object o) Unknown
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) Unknown
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source, System.Delegate callback, object args, int numArgs, System.Delegate catchHandler) Unknown
WindowsBase.dll!System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, object args, int numArgs) Unknown
WindowsBase.dll!MS.Win32.HwndSubclass.SubclassWndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam) Unknown
[Native to Managed Transition]
[Managed to Native Transition]
WindowsBase.dll!System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(ref System.Windows.Interop.MSG msg) Unknown
WindowsBase.dll!System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame frame) Unknown
WindowsBase.dll!System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame frame) Unknown
WindowsBase.dll!System.Windows.Threading.Dispatcher.Run() Unknown
PresentationFramework.dll!System.Windows.Application.RunDispatcher(object ignore) Unknown
PresentationFramework.dll!System.Windows.Application.RunInternal(System.Windows.Window window) Unknown
PresentationFramework.dll!System.Windows.Application.Run(System.Windows.Window window) Unknown
PresentationFramework.dll!System.Windows.Application.Run() Unknown

Our assemblies are marked as ComVisible(false) for the most part.
Sometimes there are hundreds of exception being thrown when opening a menu and usually they do not cause problems other than making the debug experience miserable.