JanVargovsky
commented
5 years ago Isn't "dotnet/winforms" supposed to target to "https://github.com/dotnet/winforms/issues" instead of "https://github.com/dotnet/core/issues". Same for wpf?
Closed vivmishra closed 5 years ago
JanVargovsky
commented
5 years ago Isn't "dotnet/winforms" supposed to target to "https://github.com/dotnet/winforms/issues" instead of "https://github.com/dotnet/core/issues". Same for wpf?
karelz
commented
5 years ago @JanVargovsky thanks for your report! @vivmishra fixed it.
Rand-Random
commented
5 years ago Release Notes? Maybe I am blind but I can't find release notes on the linked page.
karelz
commented
5 years ago @Rand-Random the page itself is the "Release Notes", it is not just "known issues", but info about the release bits, etc. See the same pattern in other releases: https://github.com/dotnet/core/tree/master/release-notes
@vivmishra @leecow I have noticed that we have "hanging" "known issues" doc in 3.0 and 2.2. It is not linked from anywhere AFAIK. Is that on purpose this way? Or should it be linked from each release or the main page in each release train?
jonstelly
commented
5 years ago I think the issue is that the release notes don't seem to tell us anything. Previous preview releases of dotnet core have been accompanied by at least a blog post laying out what's included, is such a blog post imminent for 3.0 preview 1?
For instance, in the original announcement for .net core 3.0 there was talk about new build tools/process for embedding the .net core runtime in your app's executable (single file distribution)... Is that available in preview 1? If so, is there a guide somewhere that explains what we need to do for that?
Rand-Random
commented
5 years ago @karelz Seems like we have different understanding about Release Notes, you seem to understand a "Note about a Release" which the linked page is, since the only Information I get there is that a release happened.
I understand, just as @jonstelly is implying, that the Release Notes, contain Information whats inside the release, what are the changes, what are the highlights and as you mentioned what are the "known issues".
So, yeah it lacks Information in my opinion - hence the confusion.
karelz
commented
5 years ago The blog post is linked from the release notes. It is just not super-clearly labeled. I am fixing that in #2110. BTW: I also added to the top post for reference.
I don't think we have more details to share than what is in the blog post - I let @vivmishra @leecow to have final word here though.
feipeng8848
commented
5 years ago can't run winform project on manjaro, dose it support Linux？
[kun@kun-pc testdotnet3]$ dotnet new winforms
The template "Windows Forms Application" was created successfully.
Processing post-creation actions...
Running 'dotnet restore' on /home/kun/WorkSpace/testdotnet3/testdotnet3.csproj...
Restoring packages for /home/kun/WorkSpace/testdotnet3/testdotnet3.csproj...
Generating MSBuild file /home/kun/WorkSpace/testdotnet3/obj/testdotnet3.csproj.nuget.g.props.
Generating MSBuild file /home/kun/WorkSpace/testdotnet3/obj/testdotnet3.csproj.nuget.g.targets.
Restore completed in 167.16 ms for /home/kun/WorkSpace/testdotnet3/testdotnet3.csproj.
Restore succeeded.
[kun@kun-pc testdotnet3]$ dotnet run
/home/kun/dotnet/sdk/3.0.100-preview-009812/Sdks/Microsoft.NET.Sdk.WindowsDesktop/targets/Microsoft.NET.Sdk.WindowsDesktop.targets(14,2): error MSB4019: The imported project "/home/kun/dotnet/sdk/3.0.100-preview-009812/Sdks/Microsoft.NET.Sdk.WindowsDesktop/targets/Microsoft.WinFX.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [/home/kun/WorkSpace/testdotnet3/testdotnet3.csproj]
The build failed. Please fix the build errors and run again.
LindaLawton
commented
5 years ago I just installed this last night and noticed a few minor issues.
Windows installer out of date
The installer needs an update. All of the links are out of date.
Visual studio support
Visual Studio also doesn't appear to see that i have .net core 3.0 installed, so i cant create projects that way. I have tried creating several of the project types using CLI they wont load in Visual studio 2017 but will load in VS code.
All of this is fine if its to early to expect Visual Studio support. However you may want to add it to the documentation someplace. I only use Visual studio professional and assumed it would have worked out of the box. I have not seen any information about Visual studio not yet being supported and that we should use VS Code. This could of course simply be an over site on my part.
Update: just found a note about WPF and Win forms projects in 2019 preview.
You can also open, launch and debug WPF and Windows Forms projects in Visual Studio 2019 Preview
LindaLawton
commented
5 years ago @feipeng8848
WPF and Windows Forms can now be used with .NET Core. They ship in a new component called “Windows Desktop” that is part of the Windows version of the SDK. (see Announcing .NET Core 3 Preview 1 and Open Sourcing Windows Desktop Frameworks)
No you cant use Windows forms on Linux.
agoni1212
commented
5 years ago Fails to install DotNetCore 3.0 Windows Server Hosting with Error 0x80070570 I download the installer on three computer separately , and all failed with the error 0x80070570 OS: Windows Server 2012 R2 Datacenter WIndows server 2016 Datacenter Windows 10
the log as follows
[0658:06FC][2018-12-06T17:09:39]i001: Burn v3.11.1.2318, Windows v10.0 (Build 14393: Service Pack 0), path: C:\Windows\Temp{CD2F4FDE-5F51-4C31-B31D-AB4F638DBE91}.cr\dotnet-hosting-3.0.0-preview-18579-0056-win.exe [0658:06FC][2018-12-06T17:09:39]i000: Initializing string variable 'BundleNameShort' to value 'Microsoft .NET Core 3.0.0 Preview Build 18579-0056' [0658:06FC][2018-12-06T17:09:39]i000: Initializing string variable 'BundleNameSub' to value 'Windows Server Hosting' [0658:06FC][2018-12-06T17:09:39]i000: Initializing numeric variable 'OPT_NO_ANCM' to value '0' [0658:06FC][2018-12-06T17:09:39]i000: Initializing numeric variable 'OPT_NO_FTS' to value '0' [0658:06FC][2018-12-06T17:09:39]i000: Initializing numeric variable 'OPT_NO_LTS' to value '0' [0658:06FC][2018-12-06T17:09:39]i000: Initializing numeric variable 'OPT_NO_SHAREDFX' to value '0' [0658:06FC][2018-12-06T17:09:39]i000: Initializing numeric variable 'OPT_NO_RUNTIME' to value '0' [0658:06FC][2018-12-06T17:09:39]i000: Initializing numeric variable 'OPT_NO_X86' to value '0' [0658:06FC][2018-12-06T17:09:39]i000: Initializing string variable 'InstallResetIISState' to value 'disable' [0658:06FC][2018-12-06T17:09:39]i000: Initializing string variable 'InstallNoIISState' to value 'disable' [0658:06FC][2018-12-06T17:09:39]i000: Initializing string variable 'ModifyResetIISState' to value 'disable' [0658:06FC][2018-12-06T17:09:39]i000: Initializing string variable 'ModifyNoIISState' to value 'disable' [0658:06FC][2018-12-06T17:09:39]i009: Command Line: '-burn.clean.room=C:\Users\Administrator\Downloads\dotnet-hosting-3.0.0-preview-18579-0056-win.exe -burn.filehandle.attached=464 -burn.filehandle.self=468' [0658:06FC][2018-12-06T17:09:39]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Administrator\Downloads\dotnet-hosting-3.0.0-preview-18579-0056-win.exe' [0658:06FC][2018-12-06T17:09:39]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\Administrator\Downloads' [0658:06FC][2018-12-06T17:09:39]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939.log' [0658:06FC][2018-12-06T17:09:39]i000: Setting string variable 'WixBundleName' to value 'Microsoft .NET Core 3.0.0 Preview Build 18579-0056 - Windows Server Hosting' [0658:06FC][2018-12-06T17:09:39]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation' [0658:1660][2018-12-06T17:09:40]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033 [0658:1660][2018-12-06T17:09:40]i000: Setting version variable 'WixBundleFileVersion' to value '3.0.0.0' [0658:06FC][2018-12-06T17:09:40]i100: Detect begin, 8 packages [0658:06FC][2018-12-06T17:09:40]i000: Setting string variable 'IISCoreWebEngineInstalled_x86' to value '1' [0658:06FC][2018-12-06T17:09:40]i000: Setting string variable 'IISW3SVCInstalled_x86' to value '1' [0658:06FC][2018-12-06T17:09:40]i000: Setting string variable 'IISCoreWebEngineInstalled_x64' to value '1' [0658:06FC][2018-12-06T17:09:40]i000: Setting string variable 'IISW3SVCInstalled_x64' to value '1' [0658:06FC][2018-12-06T17:09:40]i052: Condition 'NOT (((IISCoreWebEngineInstalled_x86=1) AND (IISW3SVCInstalled_x86=1)) OR ((IISCoreWebEngineInstalled_x64=1) AND (IISW3SVCInstalled_x64=1)))' evaluates to false. [0658:06FC][2018-12-06T17:09:40]i052: Condition '((IISCoreWebEngineInstalled_x86=1) AND (IISW3SVCInstalled_x86=1)) OR ((IISCoreWebEngineInstalled_x64=1) AND (IISW3SVCInstalled_x64=1))' evaluates to true. [0658:06FC][2018-12-06T17:09:40]i000: Setting string variable 'InstallResetIISState' to value '1' [0658:06FC][2018-12-06T17:09:40]i052: Condition 'NOT (((IISCoreWebEngineInstalled_x86=1) AND (IISW3SVCInstalled_x86=1)) OR ((IISCoreWebEngineInstalled_x64=1) AND (IISW3SVCInstalled_x64=1)))' evaluates to false. [0658:06FC][2018-12-06T17:09:40]i052: Condition '((IISCoreWebEngineInstalled_x86=1) AND (IISW3SVCInstalled_x86=1)) OR ((IISCoreWebEngineInstalled_x64=1) AND (IISW3SVCInstalled_x64=1))' evaluates to true. [0658:06FC][2018-12-06T17:09:40]i000: Setting string variable 'ModifyResetIISState' to value '1' [0658:06FC][2018-12-06T17:09:40]i052: Condition 'DotNetRedistLtsProductVersion_x64 = v24.0.27122' evaluates to false. [0658:06FC][2018-12-06T17:09:40]i052: Condition 'DotNetRedistLtsProductVersion_x86 = v24.0.27122' evaluates to false. [0658:06FC][2018-12-06T17:09:40]i101: Detected package: AspNetCoreModule_x86, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: AspNetCoreModule_x64, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: AspNetCoreModuleV2_x86, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: AspNetCoreModuleV2_x64, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: DotNetRedistLts_x64, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: DotNetRedistLts_x86, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: AspNetCoreSharedFramework_x86, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i101: Detected package: AspNetCoreSharedFramework_x64, state: Absent, cached: None [0658:06FC][2018-12-06T17:09:40]i199: Detect complete, result: 0x0 [0658:1660][2018-12-06T17:09:40]i000: Disable control InstallNoIIS [0658:1660][2018-12-06T17:09:43]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1 [0658:06FC][2018-12-06T17:09:43]i200: Plan begin, 8 packages, action: Install [0658:06FC][2018-12-06T17:09:43]i052: Condition 'NOT VersionNT64 AND (VersionNT >= v6.1) AND (IISCoreWebEngineInstalled_x86=1) AND (IISW3SVCInstalled_x86=1) AND (NOT OPT_NO_ANCM)' evaluates to false. [0658:06FC][2018-12-06T17:09:43]i052: Condition 'VersionNT64 AND (VersionNT64 >= v6.1) AND (IISCoreWebEngineInstalled_x64=1) AND (IISW3SVCInstalled_x64=1) AND (NOT OPT_NO_ANCM)' evaluates to true. [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleRollbackLog_AspNetCoreModule_x64' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_000_AspNetCoreModule_x64_rollback.log' [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLog_AspNetCoreModule_x64' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_000_AspNetCoreModule_x64.log' [0658:06FC][2018-12-06T17:09:43]i052: Condition 'NOT VersionNT64 AND (VersionNT >= v6.1) AND (IISCoreWebEngineInstalled_x86=1) AND (IISW3SVCInstalled_x86=1) AND (NOT OPT_NO_ANCM)' evaluates to false. [0658:06FC][2018-12-06T17:09:43]i052: Condition 'VersionNT64 AND (VersionNT64 >= v6.1) AND (IISCoreWebEngineInstalled_x64=1) AND (IISW3SVCInstalled_x64=1) AND (NOT OPT_NO_ANCM)' evaluates to true. [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleRollbackLog_AspNetCoreModuleV2_x64' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_001_AspNetCoreModuleV2_x64_rollback.log' [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLog_AspNetCoreModuleV2_x64' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_001_AspNetCoreModuleV2_x64.log' [0658:06FC][2018-12-06T17:09:43]i052: Condition 'VersionNT64 AND (NOT OPT_NO_RUNTIME)' evaluates to true. [0658:06FC][2018-12-06T17:09:43]w321: Skipping dependency registration on package with no dependency providers: DotNetRedistLts_x64 [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLog_DotNetRedistLts_x64' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_002_DotNetRedistLts_x64.log' [0658:06FC][2018-12-06T17:09:43]i052: Condition '(NOT OPT_NO_RUNTIME) AND (NOT OPT_NO_X86)' evaluates to true. [0658:06FC][2018-12-06T17:09:43]w321: Skipping dependency registration on package with no dependency providers: DotNetRedistLts_x86 [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLog_DotNetRedistLts_x86' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_003_DotNetRedistLts_x86.log' [0658:06FC][2018-12-06T17:09:43]i052: Condition '(NOT OPT_NO_SHAREDFX) AND (NOT OPT_NO_X86)' evaluates to true. [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleRollbackLog_AspNetCoreSharedFramework_x86' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_004_AspNetCoreSharedFramework_x86_rollback.log' [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLog_AspNetCoreSharedFramework_x86' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting__20181206170939_004_AspNetCoreSharedFramework_x86.log' [0658:06FC][2018-12-06T17:09:43]i052: Condition 'VersionNT64 AND (NOT OPT_NO_SHAREDFX)' evaluates to true. [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleRollbackLog_AspNetCoreSharedFramework_x64' to value 'C:\Users\ADMINI1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_005_AspNetCoreSharedFramework_x64_rollback.log' [0658:06FC][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLog_AspNetCoreSharedFramework_x64' to value 'C:\Users\ADMINI~1\AppData\Local\Temp\dd_dd_DotNetCoreWinSvrHosting20181206170939_005_AspNetCoreSharedFramework_x64.log' [0658:06FC][2018-12-06T17:09:43]i201: Planned package: AspNetCoreModule_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None [0658:06FC][2018-12-06T17:09:43]i201: Planned package: AspNetCoreModule_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register [0658:06FC][2018-12-06T17:09:43]i201: Planned package: AspNetCoreModuleV2_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None [0658:06FC][2018-12-06T17:09:43]i201: Planned package: AspNetCoreModuleV2_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register [0658:06FC][2018-12-06T17:09:43]i201: Planned package: DotNetRedistLts_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: Yes, uncache: No, dependency: None [0658:06FC][2018-12-06T17:09:43]i201: Planned package: DotNetRedistLts_x86, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: Yes, uncache: No, dependency: None [0658:06FC][2018-12-06T17:09:43]i201: Planned package: AspNetCoreSharedFramework_x86, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register [0658:06FC][2018-12-06T17:09:43]i201: Planned package: AspNetCoreSharedFramework_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register [0658:06FC][2018-12-06T17:09:43]i299: Plan complete, result: 0x0 [0658:06FC][2018-12-06T17:09:43]i300: Apply begin [0658:06FC][2018-12-06T17:09:43]i010: Launching elevated engine process. [0658:06FC][2018-12-06T17:09:43]i011: Launched elevated engine process. [0658:06FC][2018-12-06T17:09:43]i012: Connected to elevated engine. [06F8:038C][2018-12-06T17:09:43]i358: Pausing automatic updates. [06F8:038C][2018-12-06T17:09:43]i359: Paused automatic updates. [06F8:038C][2018-12-06T17:09:43]i360: Creating a system restore point. [06F8:038C][2018-12-06T17:09:43]i362: System restore disabled, system restore point not created. [06F8:038C][2018-12-06T17:09:43]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a9498090-aec0-45d8-89d0-9668728138f7}, options: 0x7, disable resume: No [06F8:038C][2018-12-06T17:09:43]i000: Caching bundle from: 'C:\Windows\Temp{E40B18BF-1D92-41FF-9628-362FDB9B476D}.be\dotnet-hosting-3.0.0-preview-18579-0056-win.exe' to: 'C:\ProgramData\Package Cache{a9498090-aec0-45d8-89d0-9668728138f7}\dotnet-hosting-3.0.0-preview-18579-0056-win.exe' [06F8:038C][2018-12-06T17:09:43]i320: Registering bundle dependency provider: 20833f64-4bdf-36e4-b243-6cdc63660307, version: 3.0.0.0 [06F8:038C][2018-12-06T17:09:43]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a9498090-aec0-45d8-89d0-9668728138f7}, resume: Active, restart initiated: No, disable resume: No [0658:145C][2018-12-06T17:09:43]i336: Acquiring container: WixAttachedContainer, copy from: C:\Users\Administrator\Downloads\dotnet-hosting-3.0.0-preview-18579-0056-win.exe [0658:145C][2018-12-06T17:09:43]i000: Setting string variable 'WixBundleLastUsedSource' to value 'C:\Users\Administrator\Downloads' [0658:05B8][2018-12-06T17:09:44]e000: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0 [0658:145C][2018-12-06T17:09:44]e000: Error 0x80070570: Failed to begin and wait for operation. [0658:145C][2018-12-06T17:09:44]e000: Error 0x80070570: Failed to extract payload: a6 from container: WixAttachedContainer [0658:145C][2018-12-06T17:09:44]e312: Failed to extract payloads from container: WixAttachedContainer to working path: C:\Windows\Temp{E40B18BF-1D92-41FF-9628-362FDB9B476D}\26AA2EB4651182DA78BBA3097ADE3FC1A4DBE11C, error: 0x80070570. [0658:06FC][2018-12-06T17:09:44]e000: Error 0x80070570: Cache thread exited unexpectedly. [06F8:038C][2018-12-06T17:09:44]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a9498090-aec0-45d8-89d0-9668728138f7}, resume: ARP, restart: None, disable resume: No [06F8:038C][2018-12-06T17:09:44]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a9498090-aec0-45d8-89d0-9668728138f7}, resume: ARP, restart initiated: No, disable resume: No [0658:06FC][2018-12-06T17:09:44]i399: Apply complete, result: 0x80070570, restart: None, ba requested restart: No
vivmishra
commented
5 years ago Cc @natemcmaster ; @shirhatti for 3.0 hosting bundle setup issue.
shirhatti
commented
5 years ago @vivmishra Filed a separate issue to track that
arviedelgado
commented
5 years ago @LindaLawton
Visual studio support
Visual Studio also doesn't appear to see that i have .net core 3.0 installed, so i cant create projects that way. I have tried creating several of the project types using CLI they wont load in Visual studio 2017 but will load in VS code.
All of this is fine if its to early to expect Visual Studio support. However you may want to add it to the documentation someplace. I only use Visual studio professional and assumed it would have worked out of the box. I have not seen any information about Visual studio not yet being supported and that we should use VS Code. This could of course simply be an over site on my part.
Update: just found a note about WPF and Win forms projects in 2019 preview.
You can also open, launch and debug WPF and Windows Forms projects in Visual Studio 2019 Preview
For Visual Studio 2017, you may have to enable Visual Studio to use "preview" versions of .NET Core.
Tools > Options... > Projects and Solutions > .NET Core > Tick "Use previews of the .NET Core SDK" > OK
This works with Visual Studio Community 2017 v15.9.3 to solve the "Project file is incomplete. Expected imports are missing. " popup when reloading the project.
Once you loaded the project and the build failed with no errors, try deleting "Properties" under Solution Explorer.
atljoseph
commented
5 years ago BROKEN PIECE of **** Preview (on MAC). The general public is not a testing guinea pig.
install core3 preview1 on mac mkdir -p myNewProject cd myNewProject dotnet new globaljson (says 3.0.100-preview-009812) dotnet new webapi dotnet restore OR dotnet build OR dotnet run
==> BROKEN AspNetCore not in the namespace Microsoft.
==> Attempted to install Microsoft.AspNetCore.App (version 3.0) Version 3.0 was not even listed as an option. Why is this? Because someone didn't test?
Is anyone else having problems?
I cannot even create a new solution using vs for MAC (after an update today, with computer restart) ==> Create button is unresponsive.
MASSIVE FAIL IN MY OPINION.
Reminds me why I love Node so much. Others feel the same way...
atljoseph
commented
5 years ago Last login: Sat Dec 15 14:04:07 on ttys000 /Users/joseph EARTHING joseph @ ~ $ ls -la ~/Library/Logs/VisualStudio/7.0 total 288 drwxr-xr-x 7 joseph staff 224 Dec 15 13:42 . drwxr-xr-x 3 joseph staff 96 Dec 15 13:41 .. -rw-r--r-- 1 joseph staff 1299 Dec 15 13:41 AndroidTools.2018-12-1513-41-55.log -rw-r----- 1 joseph staff 77052 Dec 15 14:05 Ide.2018-12-1513-41-55.log lrwxr-xr-x 1 joseph staff 72 Dec 15 13:41 Ide.log -> /Users/joseph/Library/Logs/VisualStudio/7.0/Ide.2018-12-1513-41-55.log -rw-r--r-- 1 joseph staff 327 Dec 15 13:42 Updater.log -rw-r--r-- 1 joseph staff 50 Dec 15 13:41 iOSDesigner.2018-12-1513-41-55.log EARTHING joseph @ ~ $ vi ~/Library/Logs/VisualStudio/7.0/Ide.2018-12-15__13-41-55.log
at MonoDevelop.Ide.Projects.GtkNewProjectDialogBackend.MoveToNextPage () [0x00092] in /Users/vsts/agent/2.142.1/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Projects/GtkNewProjectDialogBackend.cs:583
at MonoDevelop.Ide.Projects.GtkNewProjectDialogBackend.NextButtonClicked (System.Object sender, System.EventArgs e) [0x0001d] in /Users/vsts/agent/2.142.1/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Projects/GtkNewProjectDialogBackend.cs:83
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.
karelz
commented
5 years ago @atljoseph I understand your frustration when basics things don't work. Regardless, I'd like to ask you to be polite, constructive and follow .NET Foundation Code of Conduct (which we sadly don't have linked from this repo docs - something we should fix).
Note that 3.0 is in first Preview, so not all things work perfectly yet. We, however, welcome feedback and will be happy to address issues and make our products better.
Regarding your report:
AspNetCore not in the namespace Microsoft.
Where is it missing exactly? In IDE? Or does HelloWorld project fail to build?
Version 3.0 was not even listed as an option.
Listed where? In IDE? Which one?
Create button is unresponsive.
Based on your further reply with MonoDevelop callstack, I assume you are using MonoDevelop.
If there are bugs with .NET Core 3.0 Preview in MonoDevelop, it may be best to report your problems on MonoDevelop feedback channels (I don't even know what they are, but I can help route them once it is clear what problems with what products you're hitting).
That said, if you see dotnet command line failures, we should root-cause them first - starting here is best.
When basic things don't work, it is typically outcome of bad or corrupted installation of the product (.NET 3.0 Preview in your case), or bad/corrupted state of the machine (confirmation if it happens on other Macs would help, specific OS version might be needed, etc.).
atljoseph
commented
5 years ago I am being as polite as I can when I say your question about MonoDevelop is very much misplaced. If this machine has MonoDevelop on it, it is because Visual Studio for Mac uses MonoDevelop (I never installed it).
atljoseph
commented
5 years ago Yesterday, I downloaded the Core 3.0 preview 1 SDK onto a MAC, installed VS and SDK, then immediately ran dotnet new webapi. After that, opened the project in VS for MAC (again, it works great on Windows - It is just a piece of crap on a MAC - which is the usual state of Microsoft products for Mac).
The IDE complained that AspNetCore was not in the namespace Microsoft. Also, the csproj file did not carry a SINGLE package or framework reference. Manually added one for Microsoft.ASpNetCore.App. Fail (fail on restore due to … version mismatch in frameworks!) Could not even use VS 2019 for MAC to install the 3.0 package from Nuget. They only had < 3.0. That was even after running dotnet —info to confirm the version of the sdk used, and dotnet new globaljson to force it to use the preview.
Also, dotnet restore/build/run produced errors when attempting to build the project - immediately after the dotnet cli created the project.
VS for MAC says build 7.7.1 (build 15) - Yes, the error log mentioned MonoDevelop (I am not using MonoDevelop directly - I am using YOUR Microsoft product).
Try it yourself. Get a Mac. Download the SDK. Run dotnet new webapi. You will see that it is broken.
About the Create button being unresponsive. I later found that VS for MAC could create Core 2.X projects, but not 3.0. (This is the source of the errors in the VS error log.) What is the problem? The release said we could use VS 2019 Preview 1 with Core 3.0 Preview 1. Did you not test it before releasing? Can anyone out there get it to work? I do not see any evidence that they can yet. Please set me right on that if I am wrong. https://developercommunity.visualstudio.com/content/problem/400049/visual-studio-2019-preview-create-button-not-worki.html (this person told you about the issue immediately after Core3 Preview1 was released (the day after). Same situation ... 2 weeks later ... Are you ok with having a product in production for 2 weeks that doesn't work? I would not be ok with that.
Literally … dotnet new console works great, but for dotnet new webapi (a flagship use of your dotnet product), it produces a broken project. I can’t even hack it into building because the nuget packages are all showing for < v3.0. Have someone test this. Don’t release it to the public for them to test it. It is a preview. Not a test. Literally, I downloaded it, installed it, used it (exactly as the docs say to do), and it didn’t work...
And … GET BETTER DOCS. Sample projects are not complete. Documentation about features is not in-depth enough, and lacks simple, straight-forward examples, tutorials are not advanced enough, and the over-emphasize MVC structure over that of WebApi, causing too much complication when trying to learn something that should be more simple. This is where most Node projects shine a little brighter than AspNetCore.
Regards,
Joseph
atljoseph
commented
5 years ago If your repo doesn’t provide a link to such code of conduct, then it is assumed that the code of conduct does not exist. People do not know what they don’t know (or what you never told them in the first place). Again. DOCUMENTATION is crucial. Otherwise, it is futile to even go through with the act of building the product. You might think I am being mean or "going off", but that is just someone being Real with you! Adoption requires that the technology is actually adoptable by the people that might adopt it... By the way, the world really runs on Linux. Windows is the cherry on top. It is not the cake itself.
richlander
commented
5 years ago We intend to add support for .NET Core 3.0 in Visual Studio for Mac 8.0. We hope for this support to first show up in Visual Studio for Mac 8.0 Preview 2. Until that time, we recommend using Visual Studio Code on macOS instead if you want to use .NET Core 3.0.
I just tried WebAPI on macOS in terminal. It works. That's the experience that we are providing (and tested) for Preview 1. We will build on that for Preview 2 and following.
atljoseph
commented
5 years ago Thanks @richlander. It was not working correctly until all traces of previous dotnet SDK's were removed.
jskeet
commented
5 years ago Guidance on using the preview from Travis would be welcome. I've got a certain distance in NodaTime by downloading the tgz file and following the instructions, but then any tests that use the netcoreapp2.x fail because only the 3.0 preview runtime is discovered. Unlike on Windows where the installer sets everything up happily to run side-by-side, the instructions for Linux effectively create a compartmentalized installation directory. I've bodged it together, but I'm not convinced it's necessarily correct:
curl -o preview-sdk.tgz https://download.visualstudio.microsoft.com/download/pr/9f071c35-36b4-48c9-bcc2-b381ecb6cada/5be4784f19c28cb58f8c79219347201a/dotnet-sdk-3.0.100-preview-009812-linux-x64.tar.gz
mkdir -p $HOME/dotnet && tar zxf preview-sdk.tgz -C $HOME/dotnet
export DOTNET_ROOT=$HOME/dotnet
export PATH=$HOME/dotnet:$PATH
# Make older SDKs and runtimes available
for i in /usr/share/dotnet/sdk/*; do ln -s $i $DOTNET_ROOT/sdk; done
for i in /usr/share/dotnet/shared/Microsoft.AspNetCore.All/*; do ln -s $i $DOTNET_ROOT/shared/Microsoft.AspNetCore.All; done
for i in /usr/share/dotnet/shared/Microsoft.AspNetCore.App/*; do ln -s $i $DOTNET_ROOT/shared/Microsoft.AspNetCore.App; done
for i in /usr/share/dotnet/shared/Microsoft.NETCore.App/*; do ln -s $i $DOTNET_ROOT/shared/Microsoft.NETCore.App; done
echo "New dotnet --info"
dotnet --info(I then install the 2.2 SDK as normal, along with the 1.0.5 runtime for compatibility testing.)
ghost1372
commented
5 years ago hi is there any news about wpf designer support? Will it be available before 2019? When will the next preview be released? tnx
karelz
commented
5 years ago @ghogen it will be part of VS 2019 - see WPF repo for details: https://github.com/dotnet/wpf#status or https://github.com/dotnet/wpf/issues/188
HaidarZ
commented
5 years ago I'm having a project in progress , not yet released for production , is it somehow safe to go from netcore2.2 to netcore3.0. I'm seeking for the efcore3.0 fix for m2m relations. Advise?
karelz
commented
5 years ago @HaidarZ .NET Core 3.0 is in preview - it is not officially supported in production, so you can use it on your own risk. If you want full support, you need to wait for go-live preview (typically RC), or final release.
jkdmyrs
commented
5 years ago All the documentation I can find states .NET Core 3 will support EF6, but I do not see anything regarding EF6 in the release notes for Preview 1. Is EF6 support included in Preview 1? If not, when can we expect this?
ghost1372
commented
5 years ago @jkdmyrs ef6 not support in net core 3 but they working on ef core that work on net core 3 and its awesome https://docs.microsoft.com/en-us/ef/core/ https://github.com/aspnet/EntityFrameworkCore
Rand-Random
commented
5 years ago @ghost1372 Wrong. https://blogs.msdn.microsoft.com/dotnet/2018/12/04/announcing-net-core-3-preview-1-and-open-sourcing-windows-desktop-frameworks/
.NET Core 3 is a major update which adds support for building Windows desktop applications using Windows Presentation Foundation (WPF), Windows Forms, and Entity Framework 6 (EF6). ASP.NET Core 3 enables client-side development with Razor Components. EF Core 3 will have support for Azure Cosmos DB. It will also include support for C# 8 and .NET Standard 2.1 and much more!
@jkdmyrs Maybe there is a confusion on your side. .NET Core 3.0 will not include EF 6.0. EF 6.0 will be compiled against .NET Core 3.0. So you will have to wait till an EF 6.0 release which has changes done to run on .NET Core 3.0.
You should consider try to follow https://github.com/aspnet/EntityFramework6 Or ask your question there.
You can also see the commits done there and latest as of writing here "Remove of PowerTools" is the latest done since the prior of 20th August. So, no there is currently no EF 6.0 that runs on .NET Core 3.0 and it seems like there is still alot of work to be done.
All your found documentation is basically saying "They want to do it." but it seems to me that nothing has been done for it till now.
karelz
commented
5 years ago @ajcvickers @divega what's the word on EF6 plans?
ajcvickers
commented
5 years ago See https://github.com/aspnet/EntityFramework6/issues/271. Work has started, but it's unlikely anything will be ready to ship in the next preview.
joesun99
commented
5 years ago Hi everyone
I would like to ask how is net core 3 also supporting Windows Workflow Foundation?
Regards
WalterEbbers
commented
5 years ago When .net Core 3.0 was announced it was said it would have the ability to embed the runtime into the application executable. Yet no info is available how this can be done. Has the feature not been released or will it only be available in the final build for .net core 3.0?
As a side question, does the embedding also work for asp.net .net core hosted applications or only wpf based desktop applications?
jkdmyrs
commented
5 years ago @WalterEbbers self-contained deployments are already a thing in net core.
https://docs.microsoft.com/en-us/dotnet/core/deploying/index
Is this what you're looking for?
WalterEbbers
commented
5 years ago @WalterEbbers self-contained deployments are already a thing in net core.
https://docs.microsoft.com/en-us/dotnet/core/deploying/index
Is this what you're looking for?
Not exactly. When 3.0 was announced, the feature was announced as the dotnet runtime would be fully embeddable within the executable without having to install it. You could deliver your own current version within the application. From what i can see with self contained, this is not really the exact way. I hope someone from the project could answer the question :)
Thnx for the reply though @jkdmyrs !
ghost1372
commented
5 years ago @WalterEbbers You can release your project by right click on solution and select publish, in this case There are 2 modes, first self-contained If you select it all the required requirements will be placed next to the executable file. second is Dependent Framework that To run, you need to install the pre-requisites on the system you want. But I think your intention is to put all the requirements in the executable file If I guess right, they're working on a feature for this If I'm not mistaken, its https://github.com/dotnet/corefx
WalterEbbers
commented
5 years ago @WalterEbbers You can release your project by right click on solution and select publish, in this case There are 2 modes, first self-contained If you select it all the required requirements will be placed next to the executable file. second is Dependent Framework that To run, you need to install the pre-requisites on the system you want. But I think your intention is to put all the requirements in the executable file If I guess right, they're working on a feature for this If I'm not mistaken, its https://github.com/dotnet/corefx
If self-contained has all the runtime abilities whitout having to install the runtime than that would be cool. Although 'm still confused what they meant by embeddint the framework when they announced 3.0 last year.
jamiegs
commented
5 years ago I've just migrated an ASP.NET from .NET 2.1 to 3.0 to test it out.. it doesn't appear that symbols are being created for the application any longer. Has there been any changes that would cause that? The build is happening with in amicrosoft/dotnet:3.0.100-preview-sdk-stretch container..
svick
commented
5 years ago @WalterEbbers I believe that feature is not in the current preview and is tracked at https://github.com/dotnet/coreclr/issues/20287.
WalterEbbers
commented
5 years ago @svick Hmm okay, to bad they didn't let us know when the preview was released. Thnx :)
leecow
commented
5 years ago Preview 2 released so closing this thread. Please move any continuing conversations to the new issue.
.NET Core 3.0.0 Preview 1
Release Notes Download Blog post
Please report any issues you find with 3.0.0 Preview 1, either responding to this issue, creating a new issue or creating a new issue in one of the following repos: