Can't install MAUI workload properly on Mac with .NET SDK 8
I’m having trouble installing the .NET MAUI workload on my Mac running macOS. Despite trying different versions of the .NET SDK (8.0.401 and 8.0.400), Visual Studio Code consistently fails to detect the installation. I was removing all .net installations also using recommended tools from documentation, and installing .net SDK again from scratch. Nothing changed the situation. I have been using "dotnet workload repair" , "dotnet workload clean", "dotnet workload restore", "dotnet workload update", nothing seems to work. Here are the sample logs always ending with same error Writing workload pack installation record for Microsoft.NETCore.App.Runtime.Mono.maccatalyst-x64 version 7.0.20... Warning: Workload garbage collection failed with error: Workload version 8.0.400-baseline.24375.2 was not found.. When I have SDK 8.0.401 installed, I have had similar error. I suspect that a previous installation of Visual Studio 2022 (which included .NET 5 and .NET 6) might have left behind some configuration or components that are interfering with the current setup. Here are the steps sudo dotnet workload install maui dotnet workload list Result: No entries on the list. However when I run "sudo dotnet workload list" I see: Installed Workload Id Manifest Version Installation Source -------------------------------------------------------------------- maui 8.0.72/8.0.100 SDK 8.0.400 On VSCode I have the error on.net maui project (created from template) ".NET MAUI SDK: not found. Please check the .NET MAUI output window for more info." The output looks: .NET MAUI Workloads: Path: /usr/local/share/dotnet Version: 8.0.400 Suggested Workloads to be installed: Workload: maui-ios Workload: maui-android .NET MAUI SDK verification failed. Please try running `dotnet workload restore` from your project's directory and reopen the solution. I also get an error from C# dev kit: "Failed to restore solution." The output looks: Determining projects to restore... /usr/local/share/dotnet/sdk/8.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To build this project, the following workloads must be installed: maui-android [/Users/pbaturo/Repos/dotnet-learning/MauiFirstApplication/MauiFirstApplication/MauiFirstApplication.csproj::TargetFramework=net8.0-android] /usr/local/share/dotnet/sdk/8.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To install these workloads, run the following command: dotnet workload restore [/Users/pbaturo/Repos/dotnet-learning/MauiFirstApplication/MauiFirstApplication/MauiFirstApplication.csproj::TargetFramework=net8.0-android] I have completely no idea why I have this issue. Can anyone help me with overcoming this, please?Is it possible for the dotnet command to not publish some files?
I've received an unusual request from some users of an ASP.NET Core app. I'm using the dotnet command to clean and publish the solution, to a server in our network, using a GitHub self-hosted runner on another server. They don't want the dotnet command to publish the "appsettings.json" and "appsettings.Developer.json" files. Is there a way of preventing dotnet from publishing some files? Here's the code snippet I'm using from the YAML file: - name: Clean build run: dotnet clean $env:Solution_Name - name: Publish app run: dotnet publish -c Release $env:Solution_Name /p:PublishProfile=VaccineRegDevProfile
Microsoft.VisualStudio.Diagnostics.ServiceModelSink.dll installed by Visual studio 2022 has issue
I am using VS2022 community with latest update 17.9.6. I installed the component "Windows communication foundation" from VS installer. After it is installed, windows security reports this dll as suspicious and gives error "windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly" when I ran my WCF application (which opens a service host). I debugged it further and noticed that machine.config is added with below: <commonBehaviors> <endpointBehaviors> <Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/> </endpointBehaviors> <serviceBehaviors> <Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/> </serviceBehaviors> </commonBehaviors> I then checked the digital signature associated to this dll (in GAC). I see that the certificate validity is no more valid. Now questions here are: 1) Can someone confirm if validity of the certificate is the reason of error "windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly"? 2) If yes, how do we get new version of this dll with valid signature? NOTE: I am using windows 11 home with latest updates.
WindbgTime-travel C# .NET 8.0 app: why is RenderOptions.ProcessRenderMode = RenderMode.SoftwareOnly;
I picked up a couple of months old Visual Studio Solution and found I needed to make a few modifications to enable Time-Travel debugging. After resolving a few hurdles (startup module defined, profiling taking place in the Visual Studio solution), I finally configured the app to be x64/DEBUG. Yet even that would stop in the DirectX layers. Finally, not wanting to make any major changes to the app, I used: RenderOptions.ProcessRenderMode = RenderMode.SoftwareOnly; Then the app's dialog/window appeared when being time-travel-debugged.. Obviously, this stops the DirectX use of hardware, but I am curious - is there a better way? Sam ps, if need I fan send the call stack that the app stops on with out this line in the Application_Startup routine.Linux, 'strip' corrupt self-contained publish binary
For your knowledge (i search this community but i don't find anything related), Linux command strip -S --strip-unneeded "my_app" performed on a binary created with dotnet publish --runtime linux-x64 --self-contained true -p:PublishTrimmed=true -p:EnableCompressionInSingleFile=true corrupt the binary. Can be reproducible with any CLI program like the classic Hello World. ----------------------- In any Debian-derivated, when building a package (.deb), it will require to add an exception (in /usr/share/lintian/overrides) unstripped-binary-or-object in Lintian, otherwise .deb will throw an ERROR when installed (Lintian are called from package manager to validate the .deb package before install) ----------------------- In any Arch-derivated, makepkg perform a strip automatically ==> Tidying install... > Stripping unneeded symbols from binaries and libraries... resulting in a error when launching the binary: "Failure processing application bundle; possible file corruption." This can be avoided with options=('!strip') in PKGBUILD.Port 22 closed by your ip address remotely
Hi There I send this message to the manger people in the company here. I experiencing a problem that I need your help I was using Linux and one of my assignments require to connect to the port 22 on ssh protocol to log in on a remote url game but it was always closed by remote controle from you ip address. Please let the admin know and fix this problem for me..it is urgent need. I am using VMware of Linux Thanks
