Home
>
WinDev Forum
>
Topic
(Resolved) .NET dotnet - Issues with latest Windows 11
Posted by DerekM
|
(Resolved) .NET dotnet - Issues with latest Windows 11 February 18, 2025 01:44AM |
Registered: 7 years ago Posts: 79 |
The February 2025 Windows 11 update (version 24H2) has been reported to cause various compatibility issues.
My problem was running 32-bit .NET DLLs in a 64-bit application causing compatibility and memory management issues.
Took me a while to figure out what should have been obvious.
------------------------------------------
I resolved (most) of the PC Soft WinDev 27 .NET related issues since Windows 11 was upgraded in early February.
The resolution to this was cleaning up the application, getting rid of superfluous .NET interfaces (in particular .NET 5) - and matching all dlls used.
There are 3 technology stacks that have to work together - (WinDev, Windows 11, and .NET) and a lot of .NET interfaces with overlapping underlying dlls.
What worked well for about 3 years suddenly stopped working - likely due to new security features in Windows 11 and different memory management
I said most issue - as the WinDev IDE will still not run any .NET functions in GO mode. But I can live with that.
I have a WebDev and WinDev application that use the dotnet interface with VS C# functions to access a variety of critical (government) APIs.
Since the latest Windows 11 updates, the WinDev dotnet application no longer works (security issues and a lot of stuff - I have spent over a week on this alone).
Now - the thing is - the WebDev dotnet interface still works.
I am considering creating and exposing WebDev services to be used by the desktop (windev) application as the easiest way around this.
My main question is - does anyone in this forum use dotnet with windev/webdev and perhaps able to at least express an opinion.
I don't want to confuse anyone with too much detail at this point - but basically it seems that the WebDev dotnet is simpler than the WinDev dotnet.
This is not necessarily a PC Soft issue per se (other than as at Version 27 - I have to use a dotnet interface because some in-build encryption stuff does not work in WinDev - but works in VS) - and all this ipc stuff was never going to be easy anyway.
Would be great to hear from anyone using dot net with a windows windev/webdev environment or anyone able to express an opinion on this subject.
Cheers,
Derek
Edited 2 time(s). Last edit at 03/01/2025 06:20PM by DerekM.
My problem was running 32-bit .NET DLLs in a 64-bit application causing compatibility and memory management issues.
Took me a while to figure out what should have been obvious.
------------------------------------------
I resolved (most) of the PC Soft WinDev 27 .NET related issues since Windows 11 was upgraded in early February.
The resolution to this was cleaning up the application, getting rid of superfluous .NET interfaces (in particular .NET 5) - and matching all dlls used.
There are 3 technology stacks that have to work together - (WinDev, Windows 11, and .NET) and a lot of .NET interfaces with overlapping underlying dlls.
What worked well for about 3 years suddenly stopped working - likely due to new security features in Windows 11 and different memory management
I said most issue - as the WinDev IDE will still not run any .NET functions in GO mode. But I can live with that.
I have a WebDev and WinDev application that use the dotnet interface with VS C# functions to access a variety of critical (government) APIs.
Since the latest Windows 11 updates, the WinDev dotnet application no longer works (security issues and a lot of stuff - I have spent over a week on this alone).
Now - the thing is - the WebDev dotnet interface still works.
I am considering creating and exposing WebDev services to be used by the desktop (windev) application as the easiest way around this.
My main question is - does anyone in this forum use dotnet with windev/webdev and perhaps able to at least express an opinion.
I don't want to confuse anyone with too much detail at this point - but basically it seems that the WebDev dotnet is simpler than the WinDev dotnet.
This is not necessarily a PC Soft issue per se (other than as at Version 27 - I have to use a dotnet interface because some in-build encryption stuff does not work in WinDev - but works in VS) - and all this ipc stuff was never going to be easy anyway.
Would be great to hear from anyone using dot net with a windows windev/webdev environment or anyone able to express an opinion on this subject.
Cheers,
Derek
Edited 2 time(s). Last edit at 03/01/2025 06:20PM by DerekM.
|
Re: .NET dotnet - Issues with latest Windows 11 February 20, 2025 03:06AM |
Registered: 7 years ago Posts: 79 |
I'll just leave this note here for future reference - in case anyone runs into similar issues.
Gotta start re-writing a lot of stuff now (sheesh!)
--------------------------------------------------------------------------------------------------------------------
Since the latest Windows updates - WinDev (Vers.27) no longer works with .Net Assemblies. WebDev (Vers.27) still works fine. I have spent the last 2 weeks trying to reconfigure WinDev to process .Net Assemblies - everything from re-coding and validating the VS2022 C# assemblies - to trying every possible combination of .NET runtime. Nothing works. I tried reverting some Windows 11 updates - but it makes no difference (perhaps it does not fully revert everything as it warns). It seems to me that this is a "security" update/issue in Windows 11 - but there is absolutely no information or any way of ascertaining what really is happening (all logs checked etc.). I have tried everything that is possible without a deep insight to Windows 11 code. All the try-this routines have been exhausted. So it looks like a multi-year project has just been trashed with the Windows 11 updates. Once last attempt at looking for a solution - someone somewhere must have a clue - and is there any way to circumvent whatever "security" has been implemented. Not that basic system32 dll's like KERNELBASE.dll, ntdll.dll, and RPCRT4.dll are the usual dll's that fault (prior to any .NET faults that may also appear). This happens on 2 Windows 11 machines - one of them is brand new).
Gotta start re-writing a lot of stuff now (sheesh!)
--------------------------------------------------------------------------------------------------------------------
Since the latest Windows updates - WinDev (Vers.27) no longer works with .Net Assemblies. WebDev (Vers.27) still works fine. I have spent the last 2 weeks trying to reconfigure WinDev to process .Net Assemblies - everything from re-coding and validating the VS2022 C# assemblies - to trying every possible combination of .NET runtime. Nothing works. I tried reverting some Windows 11 updates - but it makes no difference (perhaps it does not fully revert everything as it warns). It seems to me that this is a "security" update/issue in Windows 11 - but there is absolutely no information or any way of ascertaining what really is happening (all logs checked etc.). I have tried everything that is possible without a deep insight to Windows 11 code. All the try-this routines have been exhausted. So it looks like a multi-year project has just been trashed with the Windows 11 updates. Once last attempt at looking for a solution - someone somewhere must have a clue - and is there any way to circumvent whatever "security" has been implemented. Not that basic system32 dll's like KERNELBASE.dll, ntdll.dll, and RPCRT4.dll are the usual dll's that fault (prior to any .NET faults that may also appear). This happens on 2 Windows 11 machines - one of them is brand new).