Topic: My conversion from string to double

[Coder]

Hi gile

There is not any option in Add -> existing Project and the other option that is Existing item can find the project .

[gile]

Right click the solution rather than the project (you can add a project to a solution, not to another project).

[Coder]

I am sorry , my mistake with the name of icons and buttons because I am still searching for my way in that dark and huge world of codes to have a step on its deck to start and you guys helped me a lot .

Many thanks for your great work and time .

Finally I got it loaded as you have advised me to do , but I see no difference in adding this palette to the first one , both work the same unless I am missing something important here .

Keep the great work gile , you are very famous in the world of AutoCAD programming and lots of friends of mine reading your French book in Autolisp and they very happy with it .

Thank you . 

[Jeff H]

and lots of friends of mine reading your French book in Autolisp

English version?
I'd buy it.

[gile]

English version?
I'd buy it.

It's free !!!

But in French...

[gile]

Finally I got it loaded as you have advised me to do , but I see no difference in adding this palette to the first one , both work the same unless I am missing something important here .

Sorry if I didn't clearly explain this.
The ConverterPalette_18 project was added to the solution to target AutoCAD versions prior to 2013.

Assuming the original ConverterPalette projects targets AutoCAD 2013 libraries, the generated assembly will work with A2013 to 2016 but not with prior version due to the 2013 "big split" in the AutoCAD .NET libraries.
To resolve this compatibilty issue, the ConverterPalette_18 project have been added to the solution. It references AutoCAD libraries of a prior to 2013 version (A2012 for example which is the first version supporting the Autoloader mechanism, another feature shown by this sample).
The ConverterPalette_18 project has the same folder structure as the original project which shares all source code and resources with it so that there's only one source to maintain for two different built projects. As you can see, in the ConverterPalette_18 project folders there're only links to the original ConverterPalette project source files.

[Jeff H]

English version?
I'd buy it.

It's free !!!

But in French...

Probably worth learning french, would help picking up girls also I would imagine.

[Kerry]

But in French...

Probably worth learning french, would help picking up girls also I would imagine.

And swearing sounds a little more graceful  ...

[Coder]

Finally I got it loaded as you have advised me to do , but I see no difference in adding this palette to the first one , both work the same unless I am missing something important here .

Sorry if I didn't clearly explain this.
The ConverterPalette_18 project was added to the solution to target AutoCAD versions prior to 2013.

Assuming the original ConverterPalette projects targets AutoCAD 2013 libraries, the generated assembly will work with A2013 to 2016 but not with prior version due to the 2013 "big split" in the AutoCAD .NET libraries.
To resolve this compatibilty issue, the ConverterPalette_18 project have been added to the solution. It references AutoCAD libraries of a prior to 2013 version (A2012 for example which is the first version supporting the Autoloader mechanism, another feature shown by this sample).
The ConverterPalette_18 project has the same folder structure as the original project which shares all source code and resources with it so that there's only one source to maintain for two different built projects. As you can see, in the ConverterPalette_18 project folders there're only links to the original ConverterPalette project source files.

Thank you for taking the time to explain the differences , it is very clear to me now .

Many thanks

[Coder]

Hi gile

A question come up to mind about loading a project in different Autocad releases . 

My current program should work on all Autocad releases start from 2013 up to latest version , correct ?

Suppose that I want to run my program in AutoCAD 2012 or before , how to make it working with these old releases ?

Many thanks.

[gile]

This is exactly the purpose of my upper description.

The ConverterPalette_18 project have to reference AutoCAD 2012 libraries (acdbmgd.dll and acmgd.dll from ObjectARX 2012 or AutoCAD 2012 install folder).
The ConverterPalette_18 project have also to target the corresponding Framework (4.0 for AutoCAD 2012).
The ConverterPalette_18 project must have the same folder structure as the original one but each folder contains links to the source files in the original project (right click on a folder > Add > Existing item... > browse to the corresponding folder in the original project > select the files and click "Add as link" in the Add popup).
This way you have the code source files really exists only once and are shared by the two projects. When you build the solution, both projects generates their own assembly. So, for A2012 you have to load the ConverterPalette_18.dll and for A2013+ the ConverterPalette_19.dll.

If you have a look to each project properties, you'll see that with the Release build generated assemblies are automatically directed to the ConverterPalette.bundle\Contents folder.
If you use the Autoloader mechanism with the ConverterPalette.bundle folder, the PackageContents.xml file takes care to load the right assembly for the target version.

[Coder]

Great ,

I just wanted to know how to make my program working with Autocad releases 2012 or before, when I build the program to have the .dll file to send to friends to use ?
Should I download the ObjectARX 2012 and make a reference to them to be able to run the program on older releases than Acad 2012 ?
Would the Framework number should be changed accordingly ?

I am sorry for asking you a lot

Regards

[Andrey Bushman]

I just wanted to know how to make my program working with Autocad releases 2012 or before, when I build the program to have the .dll file to send to friends to use ?

Sometimes the quality of the software can turn friends into enemies... Therefore qualitatively test your code before giving it to your friends.

AutoCAD 2009 and newer versions are interesting for me. Therefore usually I compile the same code sources for AutoCAD 2009, 2013 and 2015. These assemblies can be loaded successfully in any AutoCAD newer than 2008. Thus it is necessary to create three projects in a solution. One of them has original code source files, other two projects has the links to these code source files. Three projects is not a problem. But I want to test my code, because quality my software is important for me. So, it is necessary to add three additional projects with unit tests.

But can I be 100% sure what my code will works fine in AutoCAD 2010, 2011, 2012, 2014 and 2016 without testing in these AutoCAD versions? No, I can't and nobody can't. Therefore it is necessary to create the testing  projects for each AutoCAD newer than 2008. At this case my projects count is 3 + 8 = 11. Oh, it is big count... if it is required copy these projects to other computer, which has own locations of SDK (not the same like mine), then I must update all referenses of SDK manually. It is tiresome operation. Of course, as the decission of this problem it is possible to store local copies of the necessary DLL SDK files in each project: at this case your project will be portable [between computers].

I want to have two projects only [an extension and its unit tests] and compile it for all necessary AutoCAD versions through "a single click of mouse".  I want to have opportunity of debugging [breackpoints, etc] my code in any AutoCAD version newer than 2008 and quickly switching between them. Also, compilation result must to have a "magic button" for my tests launching in each AutoCAD version [on the local or remote machine] and getting the testing results (summary and individually) in HTML format. Besides, I want to have opportunity to compile and launch unit tests without any changes for different Testing Frameworks: Gallio and NUnit.

Should I download the ObjectARX 2012 and make a reference to them to be able to run the program on older releases than Acad 2012 ?
Would the Framework number should be changed accordingly ?

Each AutoCAD has own SDK version and target .NET Framework. About compatibility of AutoCAD and .Net Framework versions you can read here (you can translate it Russian to English through any online translator). SDK old versions you can download here. Last three versions SDK you can download from the Autodesk site. Often your extensions can be launched in other AutoCAD versions which can use the same .NET Framework version. For example, my extensions which are compiled for AutoCAD 2009 work fine for AutoCAD 2010, 2011 and 2012 (the same DLL file). Big changes was done in AutoCAD 2013.

Advice: be not lazy for reading the documentation and using of Google before your questions asking.

[Coder]

Hello Andrey Bushman

Frankly , I am lost with your reply , I am sorry .