[Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2024-01-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

--- Comment #7 from eins99  ---
Since .NET Framework and .NET Core are now merged to .NET and will not see new
development anymore, it would make sense to take in consideration to go this
way also with LO. Otherwise coming releases of LO will not work with .NET.

How to deal with backward compatibility is another question.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2024-01-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

--- Comment #6 from Mike Kaganski  ---
FTR: running the DotNet6 config from the solution from comment 0, putting a
breakpoint to loadEnv (cppu/source/uno/lbenv.cxx), when it gets called for
"cli_uno", in the call to (*fpInit)( pEnv ), it will load the cli_uno.dll,
which will load C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll (seen
in VS debugger's Output window); shortly after, an exception is thrown (no idea
if it's important); and then, some assemblies for 4.0 will load, then unload;
and finally, cli_uno.dll will unload. Neither before, nor after, it will be
impossible to put a breakpoint to uno_initEnvironment in
cli_ure/source/uno_bridge/cli_bridge.cxx.

When debugging DotNetFramework4.8 config, the uno_initEnvironment in
cli_bridge.cxx will even be called directly, not from loadEnv.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2024-01-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

Mike Kaganski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2024-01-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

--- Comment #5 from Mike Kaganski  ---
https://learn.microsoft.com/en-us/dotnet/core/porting/cpp-cli

It seems to me, that the preferrable way to move forward would be to
re-implement the cli assemblies in LibreOffice in C# or other language that
doesn't have these limitations (if it is possible). Or to have a separate set
of assemblies for .NET, as we have for .NET Framework.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2024-01-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

--- Comment #4 from li...@ejr-online.de ---
I confirm this bug for

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded

Since the bug is not yet assigned to anybody since one and a half year it seems
that the issue is not with high priority.

My question is if there is a workaround?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2024-01-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

Hossein  changed:

   What|Removed |Added

 Blocks||159125


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=159125
[Bug 159125] [META] .NET support
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2023-10-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

--- Comment #3 from truer0man  ---
Bug is still exist in 7.6.2.1 version of SDK. I'm using .NET 7.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2023-05-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

Mike Kaganski  changed:

   What|Removed |Added

 CC||sberg...@redhat.com

--- Comment #2 from Mike Kaganski  ---
I repro the problem both with net6, and netcoreapp3.1, using x64 platform. Also
the same is I use 'uno.util.Bootstrap.bootstrap()' instead of
'uno.util.Bootstrap.defaultBootstrap_InitialComponentContext()'.

If you enable the mixed-mode debugging (allowing to debug native code), and put
breakpoint to mediate_mapInterface (cppu/source/uno/lbmap.cxx), then the
problem happens in the call to

(*pUno2To->mapInterface)( pUno2To, ppOut, pUnoI, pInterfaceTypeDescr );

where VS reports that mapInterface points to {cli_uno.dll!Mapping_uno2cli}, but
you can't step into it from the code editor, and when you use disassembly to
step into, it looks like a no-op, instead of the expected Mapping_uno2cli from
cli_ure/source/uno_bridge/cli_bridge.cxx. Trying to put breakpoints in the
latter function (or anywhere in the file) is impossible (the debugger tells
that "No executable code of the debugger's target code type is associated with
this line ...").

Since the actually called code is a no-op, the ppOut will still contain a
nullptr upon returning to mediate_mapInterface, and then the "Handle is not
initialized" happens.

And here I get stuck, having no experience with all this machinery. Stephan, do
you have an idea?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2022-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

QA Administrators  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2022-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

--- Comment #1 from Vitaly  ---
Does anyone fixing this error or can say something about it?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)

2022-05-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148857

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.