What is difference between making project under /clr with CLR Empty Project and between making only file under / clr ?

Question

1.16/5 (4 votes)

See more:

What is difference between making project under /clr with CLR Empty Project and between making only file under / clr ?

To make it clear :

if you click on Visual studio new -> visual C++ -> CLR empty project .. does all output EXE or DLL will be under CLR only ? or it will mixed ?

what's difference if i start Native Empty Project and make only specific files .cpp with /clr option ... like user interface sources

Another Clear :
1- if i need to make user interface only use /clr on cpp file or start normally CLR empty project ?
2- also i need to use DirectX for example ... with native project or same in CLR empty project or native source file !!!!

ANSWER MEEEEEE CHEEEEEEEEEERSSSSSSS !!! ^^

Posted 23-Apr-15 9:49am

Member 10377426

Updated 25-Apr-15 4:01am

Richard MacCutchan

v4

Add a Solution

Comments

Philippe Mori 23-Apr-15 19:43pm

Normally, you want to avoid specifying options at the file level as it can cause all kind of problems if your are not careful enough to ensure that an header is always included with the same set of options (or does not depends on options).

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Sergey Alexandrovich Kryukov · Answer 1 · 2015-04-23T12:12:00

Well, you can create two different projects and compare the resulting project files; it tells you everything. It looks like you are talking of two different ways to created the same thing. It does not matter where you start, only the current state (all options and so on) matters.

Now, /clr does not guarantee that your code is "pure CLR", it only allows you to write and build CLI code. The way to write pure CLI code is: under "/clr" option, use only managed "ref" types (and of course you can use all primitive types, but not unmanaged pointers); put each and every method in one of those "ref" types.

—SA