Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles / programming

Changing the TargetCPU in Vulcan.net

5.00/5 (4 votes)
23 Nov 2011CPOL1 min read 15.4K  
How to use CorFlags to change the target CPU in Vulcan.net
In Vulcan.net, the target CPU is hard set to 32bit. The reason for this is that the Macro Compiler and the VOGUI classes were based on the VO 32bit compiler. But there is a way that you can mark your Vulcan.Net assemblies for "AnyCPU". You have to use the Corlib utility. Specifially you would change it by using the following format: CorFlags (filename) /32Bit-

While this is easy to do, it is not automated and you have to remember to enter the commands before you post your DLLs. Here is where the "Build Events" in the Vulcan project file comes in handy. Before you start this procedure, you will need to know the location of Corflags.exe. On my system is is in the C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin folder.


Here are the steps you will need to follow.



  1. right click on your project name and select properties.
  2. choose the "Build Events" tab
  3. enter the Post Build Events screen by clicking on the "..." beside the Post Build Events Command Line.
  4. Enter the following line: C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\corflags.exe" "$(TargetPath) /32BIT-
    (notice the "" in the line. They are important. Also you should put the location of your corflags, not mine.
  5. Click ok

Please note, This should only be done to a Vulcan.Net assembly where you are NOT using the macro compiler, RDD classes, or the VOGUI classes as they rely on the 32bit settings to function correctly.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)