Forum Widgets
Latest Discussions
Need help with ClickOnce deployment on .NET Framework 4.7.2 – "Unidentified program" warning
Hello, I have a WinForms application built on .NET Framework 4.7.2 that I'm publishing using ClickOnce from Visual Studio Community 2022 (official Microsoft version). Even after signing the application with a valid SHA256 V3 self-signed certificate, when I publish and try to install it via ClickOnce, I receive a warning saying the program is unidentified. Additionally, when I try to install the application on a machine that has antivirus software, the antivirus flags the program precisely because of the missing/certificate validation issue. How should I proceed? I'd like to know the correct way to publish with ClickOnce so that the application is fully recognized as valid by Windows, since I'm running into these antivirus validation problems. Thanks in advance for any guidance!CamposApr 24, 2026Copper Contributor41Views0likes0CommentsMSB4184: The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluate
Hi got this error now after I updated my VS IDE .... The path is not of a legal form. WinFormsSQLExamplePro C:\Program Files\dotnet\sdk\10.0.102\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Windows.targets <_WinRTRuntimeDllDirectory>$([System.IO.Path]::GetDirectoryName('%(_WinRTRuntimeDllReferencePath.FullPath)'))</_WinRTRuntimeDllDirectory> <_CsWinRTOrTargetingPackLibDirectory>$([System.IO.Path]::GetDirectoryName('$(_WinRTRuntimeDllDirectory)'))</_CsWinRTOrTargetingPackLibDirectory> Note the top most path entry contains a '%' character , whereas the 2nd path contains a '$' character... Not sure what is going on ... (happened after VS update)PieterClaassensJan 14, 2026Copper Contributor216Views0likes0CommentsEdm Model Generation Fails
Using an Azure ASP.NET MVC API from a Maui app, I am encountering the following error in the app when attempting to access the API. A few days ago, the initalization was working properly. The cloud app has been under further development, but the base api code has not been modified, only the response from the endpoints. The latest release NuGets are in use. What elements are being sought? System.TypeInitializationException: The type initializer for 'GeneratedEdmModel' threw an exception. ---> System.InvalidOperationException: Sequence contains no elements at System.Linq.ThrowHelper.ThrowNoElementsException() at System.Linq.Enumerable.First[TSource](IEnumerable`1 source) at SentryCloud.Models.Container.GeneratedEdmModel.CreateXmlReader()AlaskanRogueJan 08, 2026Copper Contributor94Views0likes0Comments.NET runtime issues - application not starting up
Hello, We have a .NET based application built using the .NET framework 8.0. The application runtimeconfig.json file shows this: MyApp.runtimeconfig.json "tfm": "net8.0", "frameworks": [ { "name": "Microsoft.NETCore.App", "version": "8.0.0" }, { "name": "Microsoft.WindowsDesktop.App", "version": "8.0.0" } ], Please note that we have Published the application and verified that only .NET version 8.0.16 components, DLLs etc are required. Anything higher than this does not show up. From the cmd prompt, the following runtimes are shown to be installed on the system: >dotnet --list-runtimes Microsoft.AspNetCore.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 8.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 8.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] However, when we try to start a Windows service which is installed as part of the application, it does not start up, and the Windows Event Viewer shows the following error: "Description: A .NET application failed. Application: MyAppControllerService.exe Path: C:\MyApp\MyAppControllerService.exe Message: You must install or update .NET to run this application. App: C:\MyApp\MyAppControllerService.exe Architecture: x64 Framework: 'Microsoft.NETCore.App', version '8.0.21' (x64) .NET location: C:\Program Files\dotnet\ The following frameworks were found: 8.0.20 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Learn more: https://aka.ms/dotnet/app-launch-failed To install missing framework, download: https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=8.0.21&arch=x64&rid=win-x64&os=win10" So, the issue is, even with Microsoft.WindowsDesktop.App 8.0.20 being installed on the system, it still asks for the .NET 8.0 Runtime (v8.0.21) to be installed. Please let me know why this is so? Since, as per this: https://learn.microsoft.com/en-us/dotnet/core/install/windows .NET Desktop Runtime includes the .NET runtime as well, and Microsoft.WindowsDesktop.App 8.0.20 is installed. Thanks in advance, JYJY_2013Nov 03, 2025Copper Contributor1.1KViews0likes1CommentHow to respond to upgrade-assistant cli prompts?
Bear with me please, I have not touched this stuff in a few years. Trying to upgrade Xamarin project to .Net Maui using CLI (latest version of VS 2022 cannot find the Upgrade assistant extension). I have downloaded the upgrade-assistant, but am not familiar with how to reply\how to make a selection of what is displayed after I enter "upgrade-assistant upgrade project-name" (it does not execute and instead displays information...see attached image). Is what is being display telling me that I need to ctrl-c out of this and re-enter the command using what they are showing? Please give me an example of using the Side-by-side upgrade. Is is also telling me that I need to do something with NuGet also on the command line? Thanks.comcastnet1935Nov 02, 2025Copper Contributor276Views0likes1Commentdotnet on linux - Signing key on ... is not bound
dotnet on linux gpg key not working.... Warning: https://packages.microsoft.com/ubuntu/25.04/prod/dists/plucky/InRelease: Policy will reject signature wi thin a year, see --audit for details Controle: https://packages.microsoft.com/ubuntu/25.04/prod/dists/plucky/InRelease: Sub-process /usr/bin/sqv returned a n error code (1), error message is: Signing key on BC528686B50D79E339D3721CEB3E94ADBE1229CF is not bound: No binding signature at time 2025-09-12T15:59:00Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00ZDutchglorySep 15, 2025Copper Contributor316Views0likes0CommentsWont install Framework ect automaticly ???
I have an app/program (an EXE-file) I made way back when King of Spade was a Knight and I've used it for years on Windows 10 where it automaticly downloaded and installed the dependencies ! Now I run it under Windows 11 ... it just DON'T ! I know I SHOULD go back and make an "install package" but isn't there a 'Work-Around' ?keldsorAug 15, 2025Brass Contributor277Views1like4CommentsTrying to add new Type to Dotnet Runtime from github
Hi I'm trying to modify the .NET runtime from github.com/dotnet/runtime. I created a copy of the Dictionary class called Dictionary2 in these source code files: C:\rt5\src\libraries\System.Collections\ref\System.Collections.cs C:\rt5\src\libraries\System.Private.CoreLib\src\System\Collections\Generic\Dictionary.cs When I use dot peek from Jetbrains, Dictionary2 exists in my System.Collections.dll, but when I import System.Collections.dll in my main console C# application, Dictionary2 gives me compiler errors. Am, I missing some code somewhere? Can you guys help me out here? Thanks!Erik343Jul 27, 2025Copper Contributor270Views4likes2CommentsDo I need to upgrade Microsoft.AspNetCore.* NuGet packages after upgrading the .NET Runtime?
Hi, I'm encountering an issue with our SCA (Software Composition Analysis) scan, which reports several known vulnerabilities in .NET Core components. Specifically, the scan detects that the following packages are still on version 8.0.0, which are flagged as vulnerable: Microsoft.AspNetCore.Authorization Microsoft.AspNetCore.Components Microsoft.AspNetCore.Http.Connections.Client Microsoft.AspNetCore.SignalR.Client The scanner recommends upgrading these packages to version 8.0.15 to resolve the issues. To address this, I upgraded the .NET Runtime on our environment to version 8.0.15. However, the SCA scan still reports the same vulnerabilities, indicating that the vulnerable component versions have not changed. My question is: Do I also need to manually upgrade the corresponding NuGet package versions in the project to 8.0.15, or is upgrading the .NET Runtime alone sufficient to ensure these components are updated as well? Any clarification would be appreciated. Thank you!MahaauDJul 08, 2025Copper Contributor262Views0likes1Comment