Also you can use Convert.ToDouble (https://msdn.microsoft.com/ru-ru/library/system.convert.todouble%28v=vs.110%29.aspx) method. But Double.TryParse method is better way, if you correctly use it:
The function Convert.ToDecimal is not available in WPF ApplicationYou are not right.
I assume you use the aliases for the System namespace. Something like this:Code - C#: [Select]At this case use this:
using yourAliase = System;Code - C#: [Select]or this:
yourAliase.Convert.ToDouble(str)Code - C#: [Select]
System.Convert.ToDouble(str)
The System.Convert is defined in the mscorlib.dll assembly.
the assembly would be automatically added to the .dll fileI know. But I don't know what you did with your project already. It is possible to forbid the automatically loading of the set of common DLL files. Read this book (http://www.amazon.com/CLR-via-4th-Developer-Reference/dp/0735667454/ref=sr_1_1?s=books&ie=UTF8&qid=1431351959&sr=1-1&keywords=Jeffrey+Richter) - it will usefull for you.
Hi,
Perhaps you can try to Remove the ConvertPalette_18 project from the solution, Built the solution and Add back the Existing project ConvertPalette_18.
and lots of friends of mine reading your French book in AutolispEnglish version?
English version?
I'd buy it.
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 .
Probably worth learning french, would help picking up girls also I would imagine.English version?
I'd buy it.
It's free (https://apps.exchange.autodesk.com/ACD/fr/Detail/Index?id=appstore.exchange.autodesk.com%3aappintroduction00e0autolisp_windows32and64%3afr) !!!
But in French...
Probably worth learning french, would help picking up girls also I would imagine.
But in French...
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.
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 ?Each AutoCAD has own SDK version and target .NET Framework. About compatibility of AutoCAD and .Net Framework versions you can read here (http://bushman-andrey.blogspot.ru/2014/04/net-autocad-net-framework-ms-visual.html) (you can translate it Russian to English through any online translator). SDK old versions you can download here (http://adn-cis.org/forum/index.php?topic=61.0). Last three versions SDK you can download (http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=785550) 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.
Would the Framework number should be changed accordingly ?