I L.O.V.E. developing on my 15” MacBook Pro, but I had some fiddling to get it just right.
Here is a quick post about how I have it configured.
Overview
- Software: Parallels for Mac (I intend to check out VMware Fusion when I get some time.)
- I don’t use a BootCamp partition.If you run Parallels from a BootCamp partiton you lose the ability to take snapshots, which I love.In the future, when working more with mobile emulators, I might find that I need to boot natively into Windows and change to working from a BootCamp partition.
Microsoft visual studio 2014 free download - Visual Studio Code, Real Studio, Valentina Studio, and many more programs. MacinCloud supports the latest Microsoft Visual Studio for Mac with Xamarin components. GET STARTED RIGHT AWAY Managed Server Plan and Dedicated Build Server Plan have Microsoft Visual Studio Community and Xamarin Community for Mac configured.; SEE THE LATEST VERSIONS IN ACTION Login and access the latest development tools.
Figure: I allocate 8 of my 16Gb of RAM and 4 of my 8 ‘virtual’ CPUs because Visual Studio is still awesomely fast, and I often use the spare Ram and CPUs for other VMs (e.g. for testing older browsers)
Figure: I have performance optimised for the VM
Figure: My sharing settings.The ‘Shared Profile’ setting determines if you integrate Windows into OSX. I don’t enjoy this experience at all.Tip: Install DropBox on OSX, not in Windows and then tick ‘Shared Cloud’
Figure: I prefer not to share my Windows application with Mac. I don’t use Coherence. I run my VM full screen and when I’m in my Visual Studio VM I don’t want to be distracted.
Figure: I turn off the Active Screen Corners. I find them annoying and prefer shortcut keys.
Figure: I sync my Windows time from OSX
Figure: I turned off all the Mission Control shortcuts, as they interfere with my Visual Studio shortcuts.
Figure: I have turned off most of the default OSX keyboard shortcuts, but find Ctrl + F2 (Focus the OSX Menu Bar) and Ctrl + F3 handy (Focus the OSX Dock)
Visual Studio 2013 For Mac
As always, I love feedback and suggestions.
The first step in building an ObjectARX application is to set up a project in Microsoft Visual Studio. This section lists the project settings and minimum files required to build a basic ObjectARX application.
Alternatively, you can create a new ObjectARX project using the ObjectARX Wizards for AutoCAD, which you can install from the ObjectARX utilsObjARXWiz directory.
Use the following settings for your project
- Set the application type to DLL.
- Specify the ObjectARX library and include file locations.
The easiest way to do this is to add the ObjectARX include and library directories to your MSVC++ environment settings (in the Microsoft Visual Studio menu under ToolsOptionsProjects and SolutionsVC++ Directories). You can also specify the locations in the Project Properties, but you'll need to include full paths to the files for every project you create.
- For all configurations (debug and release), set the runtime library for linking to Multithreaded DLL (in your project’s Property Pages under Configuration Properties folderC/C++ folderCode GenerationRuntime Library).
- For all configurations (debug and release), set the Detect 64-bit Portability Issues option to No (in your project’s Property Pages underConfiguration PropertiesC/C++ folderGeneralDetect 64-bit Portability Issues). This setting suppresses compiler warning 4311 for pointer assignments that are not 64-bit compatible. Some ObjectARX header files contain such assignments.
If you prefer, you can control this warning instead by using #pragma warning statements. See the Microsoft documentation for more information about #pragma warning statements.
- Set the output file name (in your project’s Property Pages under Configuration PropertiesLinkerGeneralOutput File) to a name with an .arx extension. If you include a DEF file with a LIBRARY statement in your project, this name should match the LIBRARY value. Note
LIBRARY statements are optional in DEF files.
- Add the ObjectARX libraries necessary for your program (in your project’s Property Pages under Configuration PropertiesLinkerInputAdditional Dependencies).
For example, the minimum code shown below requires rxapi.lib and acdb18.lib.
You will need to add source file(s) to the new project. If you already have source files or are using sample program source files, add these files.
This example shows the minimum code needed to make an ObjectARX program.
Add a new C++ source file to the project and enter the following code:
The project also needs a definition file. Add a new text file to the project and name it with a .def extension.
Enter the following code in the DEF file
The EXPORTS section should be present and must contain at least the acrxEntryPoint function (unless you have used another mechanism to export this function, like the Windows _declspec(dllexport) convention).
Using PRIVATE in the DEF file prevents these symbols from appearing in an import library for this ObjectARX application. The symbol will still appear in the application's export table, allowing AutoCAD to find and call the symbol. This is important because every ObjectARX application or Object Enabler must have its own implementation of these functions. The application gets the implementation of acrxGetApiVersion by virtue of linking to the static library rxapi.lib. If ObjectARX application app2 uses symbols from ObjectARX application app1 by linking to app1.lib, it would be an error for app2 to get its definition of acrxGetApiVersion from the app1 import library. Using PRIVATE in the DEF file will prevent this. Making certain to link to rxapi.lib prior to linking to any import library for another ObjectARX application will also prevent this.
The LIBRARY name should match the file name of the ObjectARX file you are going to create and must show an .arx extension. For example, if your desired output file name is test.arx, the LIBRARY statement in your DEF file should show the full name test.arx.
Once you have added these two source files, you can build a basic ObjectARX application.
To test the application, start AutoCAD and load the program using one of the following methods
- Use the AutoLISP function (arxload 'program_name').
- Use the ARX command.
- Use the APPLOAD command, which opens a dialog allowing you to maintain a list of applications to load/unload.
For more information, see Loading an ObjectARX Application.
Msdn
