![]() But while debugging the azure funciton using VS 2022 for Mac it is starting the azure function v3 and while looking at the source it seems it is using different azure CLI from addins come with part of visual studio 2022. I have installed Azure funciton v4 and ie the default runtime for the azure function core tools. how to undo all the bad things that started to happen since I tried to publish application? ![]() How to decouple Rebuild from publishing and how not to do publishing during Rebuild time? And how to restore dlls from NuGet packages in my Debug directory? I.e. SignTool Error: Invalid option: /fd, as a result I can not even rebuild my exe file. And this publishing fails with Failed to sign bin\Debug\app.publish\MyApplication.exe. And now the Visual Studio tries to publish application each time I am trying rebuild my project.dlls from NuGet packages have been delete, as a result I can not run my exe file any more.So - after I tried to publish application 2 bad things happened: SignTool Error: Invalid option: /fd and I could see that all the dll, pdb and xml files are deleted from my Debug directory and new directory bin\Debug\app.publish has been created but with the exe file only. ![]() I received error message Error An error occurred while signing: Failed to sign bin\Debug\app.publish\MyApplication.exe. My project succesfully compiles, can be debugged and executed. NET 4.6.1 Console application with NuGet packages in with Visual Studio 2019 Community Edition and VS places all the NuGet-retrieved dll and compiled pdb, xml files in src/Debug directory. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |