Generating strongly typed resource files not currently supported on .NET Core MSBuild

[livarcocc]

From @iSazonov on July 6, 2017 13:41

What is a right repo to ask about ResGen in dotnet build?

Currently I try to generate strongly typed resources and get error:
C:\Users\user\AppData\Local\Microsoft\dotnet\sdk\2.0.0-preview2-006502\Microsoft.Common.CurrentVersion.targets(2921,5): error : Generating strongly typed resource files not currently supported on .NET Core MSBuild [C:\Users\user\Documents\GitHub\iSazonov\PowerShell\src\Microsoft.PowerShell.CoreCLR.Eventing\Microsoft.PowerShell.CoreCLR.Eventing.csproj]

From related Issue https://github.com/dotnet/cli/issues/819:

dotnet-resgen got replaced by the Microsoft.Net.Sdk implementation, so closing this.

Is strongly typed resources supported?

Copied from original issue: dotnet/cli#7084

[livarcocc]

From @wli3 on July 6, 2017 17:9

Hi iSazonov,
Could you try to add resx files like this? https://github.com/dotnet/sdk/blob/cd25d6bbfc2aac61cc790c511900427ac64fdaa8/TestAssets/TestProjects/KitchenSink/TestApp/TestApp.csproj#L24
(This is a part of SDK automatic test asset)

[livarcocc]

From @iSazonov on July 6, 2017 17:29

@wli3 Thanks! Please clarify - I don't see strongly typed config in the csproj.

[livarcocc]

From @wli3 on July 6, 2017 17:35

Hi @iSazonov ,
I think I misunderstood you. Looks like your project is in Github, could you share the specific strongly typed config code link?

[livarcocc]

From @iSazonov on July 6, 2017 17:41

@wli3 I'll publish the sample tomorrow from my local branch.

[livarcocc]

From @iSazonov on July 7, 2017 5:34

I published my test. See last <ItemGroup> in https://github.com/iSazonov/PowerShell/blob/cproj-psversion-from-git-resx/src/Microsoft.PowerShell.CoreCLR.Eventing/Microsoft.PowerShell.CoreCLR.Eventing.csproj

Build command:

dotnet msbuild /t:"ResGen" /v:diag /noconsolelogger /fileLogger .\Microsoft.PowerShell.CoreCLR.Eventing.csproj
or
dotnet build /t:"ResGen" /v:diag /noconsolelogger /fileLogger .\Microsoft.PowerShell.CoreCLR.Eventing.csproj

I believe error place is here
Is the project compiled without FEATURE_CODEDOM?

[livarcocc]

I am moving this issue over to MSBuild. FYI @rainersigwald

[rainersigwald]

Huh, we should have had an issue open for this already but I couldn't find one.

Is the project compiled without FEATURE_CODEDOM?

Yes, it is: CodeDOM wasn't available at the time of the initial port to .NET Core and we haven't lit up this feature after the initial port.

It looks like CodeDOM is available in .NET Core 2.0 (for code-writing scenarios, though not compilation), so we should be able to enable that feature flag everywhere after we move to targeting .NET Core 2.0.

Workarounds

Build with full framework MSBuild.exe (on a Windows machine).

Check in the (generated) .cs files and update them when necessary (from Windows/full framework).

[iSazonov]

@rainersigwald Thanks!
PowerShell Core is multiplatform project and we cannot use MSBuild.exe. Currently we use a simple tool developed by @vors.

It looks like CodeDOM is available in .NET Core 2.0

Yes, it is. So I believe it is easy to fix the Issue.

[foo-baar]

Hello Team, I am sorry if I am asking silly question: So what I understand is that if I am using dotnet sdk on my Mac & vscode for editing, I can't create a strongly typed controller from db ?

(I know there is visual studio version now available for Mac).
Thanks 👍

[iSazonov]

Team, .Net Core 2.0 RTM was out - could you please milestone the Issue?

Team, .Net Core 2.0 RTM was out - could you please milestone the Issue?