Click here to Skip to main content
15,886,873 members

Comments by Fydobas (Top 22 by date)

Fydobas 3-Aug-23 6:14am View    
Oh my *expletives*
That was it! I created a test project using .NET Framework, isolated the functionality that had to do with the library... and it worked. All this because Visual Studio 2019 onwards names the .NET Framework WPF template as "WPF *app*" and not "WPF *application*" so I didn't notice it.
*Expletives*
Fydobas 2-Aug-23 5:36am View    
Ugh. You know, I actually hate WinForms and its dated... everything, so much. Yet I'm forced to use it because of stuff like this. Ugh.
Fydobas 2-Aug-23 4:03am View    
To misquote Tenacious D... the peculiar thing is this, my friend: the ERP application the library is sending data to is, almost certainly, made with .NET Core. I'm puzzled as to why the same company would only build a library for .NET Framework... I have contacted them to see if they can provide an alternative in any case
Fydobas 23-May-23 6:32am View    
I have managed to make most of it work using OWIN. Just that for some reason, I cannot get the user name using HttpContext.Current.GetOwinContext().Authentication.User.Identity.Name... it's always empty.
Fydobas 23-May-23 3:59am View    
Oh that makes complete sense. That link you provided, however, is slightly confusing as it seems to be referring to a Web API/MVC project, not Web Forms like my case - and the samples seem incomplete.