nulastudio
Doesn't work with net 9.0
When project is trageting dotnet 9.0, publishing fails with the following error:
error MSB3073: The command ""C:\Users\USER\.nuget\packages\nulastudio.netbeauty\2.1.4.6\targets\../tools/win-x86/nbeauty2.exe" --loglevel Info --usepatch "C:\src\MyApp\bin\Release\net9.0-windows\win-x64\publish\/." ./libraries " exited with code 1.
It's a WPF if it makes any difference.
I also ave trouble with .net9.0, for me it work but a lot of dll are not moved to the subfolder and stay at the root, there is a list :
"Microsoft.AspNetCore.Metadata.dll" "Microsoft.AspNetCore.WebUtilities.dll" "Microsoft.JSInterop.dll" "Microsoft.Net.Http.Headers.dll" "System.Formats.Asn1.dll" "System.Net.Http.Json.dll" "System.Text.Json.dll" "Microsoft.AspNetCore.Authorization.dll" "Microsoft.AspNetCore.Components.Authorization.dll" "Microsoft.AspNetCore.Components.dll" "Microsoft.AspNetCore.Components.Forms.dll" "Microsoft.AspNetCore.Components.Web.dll"
My app is a blazor webapp. I use visual studio 17.12
I prefered put a comment rather than open new issue because i think its better centralize all issues around .net 9.0 here.
thanks !
When project is trageting dotnet 9.0, publishing fails with the following error:
error MSB3073: The command ""C:\Users\USER\.nuget\packages\nulastudio.netbeauty\2.1.4.6\targets\../tools/win-x86/nbeauty2.exe" --loglevel Info --usepatch "C:\src\MyApp\bin\Release\net9.0-windows\win-x64\publish\/." ./libraries " exited with code 1.It's a WPF if it makes any difference.
is that ok to post the full build log here? there should be a more detail error near this line.
I also ave trouble with .net9.0, for me it work but a lot of dll are not moved to the subfolder and stay at the root
it depends on many things, but still less dlls then your post in most of time, let me collect few questions first:
- are you building or publishing?
- if publishing, are you publishing framework-dependent or self-contained?
- post the config if you could, a demo would be great
Sorry, should've given steps to reproduce.
To answer your questions:
- publishing.
- self-contained
- I've given steps to reproduce and the sample csproj content in the original post above.
I also ave trouble with .net9.0, for me it work but a lot of dll are not moved to the subfolder and stay at the root
it depends on many things, but still less dlls then your post in most of time, let me collect few questions first:
- are you building or publishing?
- if publishing, are you publishing framework-dependent or self-contained?
- post the config if you could, a demo would be great
publishing framework dependent, you will find a repro here : https://github.com/julienGrd/BlazorAppTestNetBeautyWithPdb, just checkout the project and publish and you will see these dll not moved
publishing framework dependent, you will find a repro here : https://github.com/julienGrd/BlazorAppTestNetBeautyWithPdb, just checkout the project and publish and you will see these dll not moved
that's weird, it works as expected here.
publishing framework dependent, you will find a repro here : https://github.com/julienGrd/BlazorAppTestNetBeautyWithPdb, just checkout the project and publish and you will see these dll not moved
that's weird, it works as expected here.
OK i just switch from 17.12 preview 5 to 17.12 in the stable canal, i dont' see anymore these dll at the root but neither in the libraries folder (which can be normal because i reference the package but dont use it in my code). I will take a look with my regular project how its going
OK i just switch from 17.12 preview 5 to 17.12 in the stable canal, i dont' see anymore these dll at the root but neither in the libraries folder (which can be normal because i reference the package but dont use it in my code). I will take a look with my regular project how its going
you can search that dll name in deps.json, if there is no record, then it is normal. and if your are publishing FDD and the dll is belongs to the framework, it still normal there is a record in deps.json but no dll in any app folder.
i don't see any problems in my main app, i think its was just a weird behavior by using the preview5 visual studio. For me my problem is close, thanks for your help !