olewoo | improved performance , hyperlinks | Frontend Framework library

by leibnitz27 C# Version: 1.2.6502 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | olewoo Summary

olewoo is a C# library typically used in User Interface, Frontend Framework, React applications. olewoo has no bugs, it has no vulnerabilities and it has low support. However olewoo has a Non-SPDX License. You can download it from GitHub.

Oleview's a very handy tool, but it's got some really annoying niggles (only 1 typelibrary open at once, no search, slow on large TLBs, yadda yadda) - OleWoo is my attempt at building something which drags oleview kicking and screaming into at least the late 1990s!. This might look familiar... (now hyperlinks take you to interface/type definitions...). Using the 'find symbol' search box opens a list on the right, with all matching nodes of the TypeLibrary tree - click on one to navigate to it, and view the relevant IDL. Click on the [>>>] to dismiss the list. Of course, you can CTRL+F on the IDL viewer to search (It's infuriating that that's missing from OLEVIEW!). Click 'Add new Tab' to open up another view on the typelibrary - useful when you need to flick back and forth between interfaces.

Support

Quality

Security

License

Reuse

Support

olewoo has a low active ecosystem.

It has 8 star(s) with 6 fork(s). There are 4 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 6 have been closed. On average issues are closed in 124 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of olewoo is 1.2.6502

Quality

olewoo has no bugs reported.

Security

olewoo has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

olewoo has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

olewoo releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of olewoo

Get all kandi verified functions for this library.

olewoo Key Features

No Key Features are available at this moment for olewoo.

olewoo Examples and Code Snippets

No Code Snippets are available at this moment for olewoo.

Community Discussions

Trending Discussions on olewoo

Class name in a Library being mangled when calling functions in Word Interop

How to pass an uninitialized array from VB6 to .NET via COM?

QUESTION

Class name in a Library being mangled when calling functions in Word Interop

Asked 2018-Sep-12 at 13:51

I'm having some weird trouble with a class library in my application. We have dozens of ComVisible classes and recently I've found a situation where the name of a certain class being exposed through COM is no longer coming across as it used to.

I was able to duplicate the issue in a small sample program, and the issue is related to a single line involved in Microsoft Word Interop. Specifically I have a class Window. Normally this class is ComVisible as 'Window', but if I reference the Document.ActiveWindow property in Word Interop my class becomes ComVisible as 'TestLibrary_Window'. In my real application I have 100s of places where I refer to Window, and I don't want to change them all to TestLibrary_Window, and moreso I want to understand what could possibly be going on by refering to one property changing how my library exposes itself.

I can easily demonstrate the result by looking at the TLB file using a program OleWoo (http://www.benf.org/other/olewoo/). Notice that in the Result 1 you see an entry for coclass Window, but in Result 2 you see an entry for coclass TestLibrary_Window. Result 1 is how I expect the TLB to come across and if the trouble line in my code is commented this is what I receive. Result 2 is what I get when I uncomment the trouble line.

The following is a minimal implementation that duplicates my issue. If the commented line in TestClass is left commented than I have no issue, however if I uncomment that line I have a problem. Note that in my sample code I don't need any code within the Window class to demonstrate the issue.

File 1: TestClass.vb

...

ANSWER

Answered 2018-Sep-12 at 13:51

As @TnTinMn mentioned in a comment above, the issue I was having was indeed related to the 'Embed Interop Types' on the reference to Microsoft.Office.Interop.Word. By switching this option to false my TLB is now being created as expected.

Source https://stackoverflow.com/questions/52227009

QUESTION

How to pass an uninitialized array from VB6 to .NET via COM?

Asked 2017-Sep-24 at 01:55

I want to replace a component written in VB6 with a new component written in VB.NET. The new component has to work with other VB6 applications until these are replaced as well. I'm having trouble with a function that takes string arrays as parameters.

I'm using a VB6 class that contains this function to replicate the problem:

...

ANSWER

Answered 2017-Sep-24 at 01:55

I believe that this is a bug in the .NET Framework.

I attached a debugger to the VB6 application. This is the stack trace at the moment of the crash:

This is the disassembled code at that location:

That is the function DispatchInfo::IsVariantByrefStaticArray. It dereferences the result of (*V_ARRAYREF(pOle)) without checking if it's NULL. The member fFeatures is at offset 2 resulting in an access violation at address 0x00000002.

I believe this is the problem I stumbled upon. I think I will have to find another way to solve my original problem.

Source https://stackoverflow.com/questions/46369063

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install olewoo

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: