Comments by vickoza - CodeProject

vickoza 8-Nov-15 0:07am View

The reason I want to break is the application into libraries is to remove the dependencies, simplify the code base, add new features with worrying about how it would affect the code base and to be able to build different version of the application.

vickoza 11-Jul-15 18:01pm View

Ideally, I would like to inherit my native class defined in one C++\CLI project into another C++\CLI project that stores more native C++ objects. I have access to the source code but I do not want to move that C++\CLI class into the other project or duplicate the code into the second project.

vickoza 10-Jul-15 15:38pm View

They are native to the C++/CLI project but they are storied into different C++/CLI projects. An example is lets say you where to inherit a object from a pure native C++ library. The way to do so would be first to include the header file and then include the library if the header file provide no implementation. Is there a way to provide this type of inheritance linking with a C++\CLI?

vickoza 10-Jul-15 14:57pm View

sorry but what I mean is I cannot inherit from my native base class into another C++\CLI project because it is only defined in the original C++\CLI project. I can inherit the base class within the original C++\CLI project.

vickoza 10-Jul-15 14:31pm View

So does that mean my native base class is lost and I cannot inherit from C++/CLI native classes?

vickoza 10-Jul-15 14:10pm View

That defeats my point my base native class has handles to cli classes wrapper. "ref" types cannot inherit from native types. What I want to do is to extent my base native class and to generate new a derived handle

vickoza 10-Jul-15 10:29am View

I would like to reference the native class in another C++/CLI project. This class inherit from a native C++ class with so the ref is invalid also I do not want to expose this class to C# or other .Net languages directly but rather through handles expose this class

Comments by vickoza (Top 7 by date)