Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes. In your project properties, there is a page that indicates the runtime. There is a drop down that lists all of the runtimes available. Choose the one that is appropriate for you. (For VS 2008: Right click on the project -> properties, Compile tab, Advanced Compiler Settings button -> Target framework)</p> <p>We do this right now. We would like to move to VS 2008, but we are doing it incrementally. So right now we have a VS 2008 solution, but all the projects still target .Net 2.0. Thus, when we compile and deploy, we don't need the .Net 3.5 stuff installed on our test boxes.</p> <p><strong>UPDATE:</strong></p> <p>To force a native program to link to specific versions of .dlls, you probably want to use something like this:</p> <pre><code>#pragma message ("Explicit link to generate a manifest entry for MFC.") #if defined (_DEBUG) #pragma comment(linker, "\"/manifestdependency:type='win32' name='Microsoft.VC80.DebugMFC' version='8.0.50608.0' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b'\"") #else #pragma comment(linker, "\"/manifestdependency:type='win32' name='Microsoft.VC80.MFC' version='8.0.50608.0' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b'\"") #endif </code></pre> <p>Except, that instead of MFC, you should find the correct values for the .Net .DLLs.</p> <p>It is reasonable to believe that you cannot have .Net 2.0 SP1 and .Net 2.0 on the same box. So getting this to work on that box is likely going to be really, really painful. It is probably better to spin up a new build VM that you can install the old, unpatched .Net framework on (if you can even get a hold of it anymore.) </p> <p>Otherwise you will need to copy all the build-time files over to your current box, and then make adjustments to the include and library paths based on your build type. Probably this is a much bigger headache than it's worth.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I target a specific version of the C++ runtime?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChristopher
    1. USChristopher
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI believe that only works for .Net projects. I don't think that works for a unmanaged C++ project. I've always found Visual Studio to target the latest version of the runtime when compiling C++ code.
      singulars
      1. PO
      1. USSoo Wei Tan
    2. COCorrect...that only works for managed projects. I wish it were that easy for unmanaged. :)
      singulars
      1. PO
      1. USJohn Clayton
    3. COSorry, I thought you wanted managed C++. You can do similar things for native C++ by choosing which SDK you are targetting. This basically involves setting the correct compiler paths. For VS2005 there is a batch file called vcvars.bat Are you using makefiles to build, or devenv?
      singulars
      1. PO
      1. USChristopher
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload