OK, so that's Publishing the app. Click on the file once in Solution Explorer and change the "Build Type" from "Content" to "None" and change "Copy to output Directory" to "Do not copy". If that doesn't do it for you, there's another way to exclude files from the Publish, described at Excluding Files and Folders from Deployment | Microsoft Learn[^]. Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

Since it's web-based, Bootstrap icons are here: Bootstrap Icons · Official open source SVG icon library for Bootstrap[^] They are colorable. Do Ctrl+F if you don't see something. ("Exclam" for exclamation mark; octagon for stop sign.) Thermometer might be interesting but probably vague.

Found the issue. For anyone who runs across this or similar problem with an HTTP-Triggered Azure function in the future it may be because you are running the function in isolated worker mode. If so you must change the footprint of the function to look for an HttpRequestData object rather than an HttpRequest object in the Run parameters and return a HttpResponseData object like this: [Function(nameof(myHttpTriggeredFunction))] public static HttpResponseData Run([HttpTrigger(AuthorizationLevel.Anonymous, "post")] HttpRequestData req, FunctionContext executionContext) { // processing code here } There are no solutions, only trade-offs.    - Thomas Sowell A day can really slip by when you're deliberately avoiding what you're supposed to do.    - Calvin (Bill Watterson, Calvin & Hobbes)

of course, developers would have to debug it. Hey, I have an idea. Maybe Microsoft should follow a basic UI principle. If it won't work or is not supported, don't let the user select it. The alternative might be to point out the issue with more details. But nah, I don't expect that of Microsoft. Jeesh. fwiw, this crap seems to be culturally embedded within Microsoft. COM, COM+, DCOM, ActiveX (another variant of COM), etc. They never learn; however, they can embed advertisements in my toolbar. :mad: Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.

Maybe you could create a local, non admin account and launch Edge under that account? That would detach your work id? I thought it was an email as well until I broke out the magnifier and saw the handle. Now a days, they should have used a back pack icon! Briefcase is from Win3.1/95

I found the answer and solution elsewhere, posted below in case this is useful to anyone else. The object in the second blazor component being clicked on was an HTML anchor element: <a href="#" class="nav-link btn-link" @onclick="(()=>ShowDetails(app.Id))"> Because an anchor is a navigation element, it has a default action which is to navigate somewhere, in this case to "#" which means to stay on the current page. Blazor is a single-page application so navigating to itself reloads the default "page" which is Index.razor. To stop that default action the solution is to add the @onclick:preventDefault directive to the anchor element: <a href="#" class="nav-link btn-link" @onclick="(()=>ShowDetails(app.Id))" @onclick:preventDefault> Of course, another solution to consider is using a non-navigation HTML element such as a button. There are no solutions, only trade-offs.    - Thomas Sowell A day can really slip by when you're deliberately avoiding what you're supposed to do.    - Calvin (Bill Watterson, Calvin & Hobbes)

Server accounts management, portfolio, is macros, in instantiated form, of overruling.

I mean, at least once every 10 years you gotta bust out the Super Metroid. Jeremy Falcon

Yeah, working with blobs like that is a drag. I don't really work with blobs outside of my code anymore. I can delete all or a few manually, but for that kind of work I write a quick console application that does the work for me :~ Luckily I rarely do that kind of stuff, it's mostly a few :) Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript

I have several times written code that was greatly simplified by explicitly ignoring errors after 'optional' operations. A trivial example: If a personal user profile is available, use it to initialize the environment. If it is not, it really doesn't matter why not (in some environments, it might matter, but not in my cases). Otherwise, if an installation default profile is available, use that. If not, ignore the reason why it is not available, and use a hardcoded default profile. The application comes up running; that's the important thing for the user. Failing startup with a complex explanation that a user won't understand anyway is far less satisfactory. For a first-time user, there will be no user profile; it is created from the first or second fallback. Defining an installation default profile is optional (and for a PC with a single user, it doesn't make sense), and setting it up requires far more understanding than from a first time user. The #1 reason why the two first steps may fail is "It hasn't been created yet". I have not yet experience any other reason that a first time user would be able to fix even if the error message was displayed. When the user exits the application, the personal profile is saved. Now, thorough checks are made. If there are conditions making that impossible, it will probably reveal the reason why the startup reading of the profile (which should have been there - the user is a returning one) failed. This happens very rarely, and doesn't bother the first time user. I have never experienced any case where reading a profile would fail but writing would succeed for any other reason than that it doesn't exist and will be created. So any other problem will be detected - without stopping the user from doing his work (although under a default profile). You might argue: But for your own purposes, you should log the problem, even if you don't display the error to the user. That log would, in 99,9% of all cases, tell me: Reading user profile failed because this is a first-time user. Reading installation default profile failed because no installation default profile has been created. Well, I know that! I don't need a log file to tell me! For other failure reasons, the error report from saving the user profile will be good enough. This reading of a user profile is one of three or four cases of "See if you can do the operation. If you cannot, it isn't a big deal - maybe even expected - so don't bother the user with it". Another case that comes to m

Which version of C# / Visual Studio are you using? private void TestFunction(object unknownClass) { (MyBase localObject, string specificProperty) = unknownClass switch { ClassOne c1 => (c1, c1.ClassOneProperty), ClassTwo c2 => (c2, c2.ClassTwoProperty), MyBase b => (b, null), _ => (null, null), }; if (localObject is null) { Console.WriteLine($"Unknown object: {unknownClass}"); } else { Console.WriteLine($"Common Property = {localObject.CommonProperty}, Specific Property = {specificProperty}."); } } "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

I suspect there is no missing assembly, in spite of the myriad "All probing URLs attempted and failed." messages. The package runs, but causes the app to exit when it attempts to execute one of the package's main functions. No errors, no log entries, no event logs, just exits from Debug mode. If you think 'goto' is evil, try writing an Assembly program without JMP.

Well, yesterday’s puzzle almost was like Absurdle, where the game refuses to accept your answer by switching words,

TNCaver wrote: Quite a number of my repos aren't pushed to DevOps because the apps are non-productions one-offs, or educational, or laboratories for experimenting with new tools, and I need another way to back them up. You could look into any of the free Git providers (GitHub, GitLab, Bitbucket). They all have a free tier with quite sizeable private repo offerings. TNCaver wrote: I don't always want o commit and push at the end of the day. Maybe I should. Yes, you should. Half ranting here: I know there is kind of a "shame" to push on private branches half finished work and stuff that is still not right. Besides the obvious safety advantage, in the long run, I find that commit history shows more about the development process and difficulties encountered than a single large commit with a short message. And for the shame part: we all make mistakes and there is no shame in finding and fixing our mistakes. It's always a learning process. Mircea

That part actually makes sense: the extension methods are defined in the assemblies they're used for. Otherwise, all of the classes to configure eg: logging would need to be included in the DI assembly, which would be an absolute mess. :) For the Microsoft extensions I've seen, the class where the extension methods are defined is usually deliberately added to the Microsoft.Extensions.DependencyInjection namespace, even though that's not the correct namespace for the assembly. That way, you don't have to add extra using statements to your code to configure the services; you just need a reference to the assembly. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Yep, did that at the beginning of my troubleshooting. All 20 package DLLs are in the same folder as the exe, just as all the previous DLLs it has been using all along have been. All the correct versions, copied from the obj\x64\Release folder where they were pushed to when I built the project. If you think 'goto' is evil, try writing an Assembly program without JMP.

Thanks, I'm still fairly new to Git, and didn't know about post-checkout hooks. This is promising! If you think 'goto' is evil, try writing an Assembly program without JMP.

Maybe this will help. IoC is a design/architecture concept, DI is an implementation approach. With IoC your are doing structural inversion on object lifecycles. Commonly an operating object will "new" any objects it needs and then invoke operations. With IoC the objects are supplied and the operating object invokes operations on this supplied object. So, behavior lives in the operating object, but the structure has been factored out to a higher level - inverted. Since Interfaces define behavior, they are a common construct in IoC/DI. The simplest implementation of IoC doesn't need DI. This is IoC: Class Foo { public string Bar(Decoder decoder, string inString){ return decoder.decode(inString); } } You have inverted control of lifecycle management. The caller creates and supplies the structure (the object doesn't "new" any ones it wants), and the operating object operates on these objects. More commonly, you do this in the constructor. Class Foo { readonly Decoder _decoder; public Foo(Decoder decoder){ _decoder = decoder; } public string Bar(string inString){ return _decoder.decode(inString); } } In some ways, the operating object is less dependent because it doesn't have to manage the selection and lifecycle management of the used object. This is IoC (hard coded) in a nutshell. DI is one way to address hard coding. You can think of DI as a combined Lookup and Activator. You give DI a "key", it looks up the mapped object, instantiates it using an Activator, and passes out the instance. You can have 1:1 type situations, where the Key and Value are the same. I tell it Foo, and it gives me a Foo object. Or, you can have 1:Many. Interfaces help here. Because with IoC I have decoupled the structure from the behavior, and interfaces are about behavior, I can associate many Values with a Key. interface IFoo { string Bar(string inString); } class FooOne : IFoo { } class FooTwo : IFoo { } lookup.Add(IFoo, FooOne); lookup.Add(IFoo, FooTwo); This provides another form of loosening dependencies and coupling. class Foo{ IFoo \_foo; public Foo(IFoo foo){ \_foo = foo } } The DI system "intercepts" object creation, inspects the constructor to see if any types are in the lookup, supplies those instances, and then lets the creation process resume. To your question about "new", with "new" I have to know the class and it'

Turn around... and face the music! :P