setup for Visual Studio 2008 Pro Ed. on 64-bit computer

  • Thread starter Thread starter Timothy Daniels
  • Start date Start date
T

Timothy Daniels

Guest
On-line lists of features for VS 2008 list the capability of
emitting code for 64-bit computing if VS is installed on a
64-bit computer. Does anyone know if such installation
is sufficient to cause VS to emit 64-bit code, or is there
additional parameters that must be set during installation
or at development time to cause VS to emit 64-bit code?

*TimDaniels*
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

Please provide a link about 'emitting 64-bit code' because this sounds
rather strange.


Timothy Daniels wrote:
> On-line lists of features for VS 2008 list the capability of
> emitting code for 64-bit computing if VS is installed on a
> 64-bit computer. Does anyone know if such installation
> is sufficient to cause VS to emit 64-bit code, or is there
> additional parameters that must be set during installation
> or at development time to cause VS to emit 64-bit code?
>
> *TimDaniels*
>
>
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

As far as I'm aware, the regular release version that you buy does compile
to 64bit. The 'Express' versions, does not! A wild guess would be that you
probably may have to configure each project that you create, to target the
necessary libraries - it's a rare thing to see software read your mind!

Please check with the Tech Net forums for more informed answers, this is
primarily a 64bit OS user forum - not a developer NG!


Tony. . .


"Timothy Daniels" <NoSpam@SpamMeNot.com> wrote in message
news:%23CIU00HNJHA.4248@TK2MSFTNGP03.phx.gbl...
> On-line lists of features for VS 2008 list the capability of
> emitting code for 64-bit computing if VS is installed on a
> 64-bit computer. Does anyone know if such installation
> is sufficient to cause VS to emit 64-bit code, or is there
> additional parameters that must be set during installation
> or at development time to cause VS to emit 64-bit code?
>
> *TimDaniels*
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

See "64-bit Development" on this webpage, and look at the
Visual Studio 2008 Professional Edition column:
http://msdn.microsoft.com/en-us/vstudio/products/cc149003.aspx .

"Emit code" is what the VS compiler does. It clearly states that
VS must run on a 64-bit computer with the 64-bit versions of the
..NET Frameworks installed, but it doesn't mention any settings
that must be made (if any) to cause it to produce code for 64-bit
apps.

*TimDaniels*

"Bobby Johnson" wrote:
> Please provide a link about 'emitting 64-bit code' because this
> sounds rather strange.
>
>
> Timothy Daniels wrote:
>> On-line lists of features for VS 2008 list the capability of
>> emitting code for 64-bit computing if VS is installed on a
>> 64-bit computer. Does anyone know if such installation
>> is sufficient to cause VS to emit 64-bit code, or is there
>> additional parameters that must be set during installation
>> or at development time to cause VS to emit 64-bit code?
>>
>> *TimDaniels*
>>
>>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

My questions is basically whether VS will emit code that is appropriate
for the machine on which the code is compiled, not whether VS can read
human minds. I did leave out that the VS available to me for purchase is
the Academic Edition of VS 2008 - which is the Professional Edition plus
examples - which is capable of 64-bit development. I'll try the Tech Net
fourms.

*TimDaniels*

"Tony Sperling" wrote:
> As far as I'm aware, the regular release version that you buy does compile to
> 64bit. The 'Express' versions, does not! A wild guess would be that you
> probably may have to configure each project that you create, to target the
> necessary libraries - it's a rare thing to see software read your mind!
>
> Please check with the Tech Net forums for more informed answers, this is
> primarily a 64bit OS user forum - not a developer NG!
>
>
> Tony. . .
>
>
> "Timothy Daniels" wrote:
>> On-line lists of features for VS 2008 list the capability of
>> emitting code for 64-bit computing if VS is installed on a
>> 64-bit computer. Does anyone know if such installation
>> is sufficient to cause VS to emit 64-bit code, or is there
>> additional parameters that must be set during installation
>> or at development time to cause VS to emit 64-bit code?
>>
>> *TimDaniels*
>>

>
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

OK, I found an MS on-line document on the subject. It says that
there is a compiler option for VS 2008 Professional (and higher)
that tells VS to emit 32-bit or 64-bit code:
http://msdn.microsoft.com/en-us/library/zekwfyz4.aspx .
There is also an option that seems to defer selection until
runtime on the targeted machine (i.e. "/anycpu").

*TimDaniels*

"Timothy Daniels" wrote:
> See "64-bit Development" on this webpage, and look at the
> Visual Studio 2008 Professional Edition column:
> http://msdn.microsoft.com/en-us/vstudio/products/cc149003.aspx .
>
> "Emit code" is what the VS compiler does. It clearly states that
> VS must run on a 64-bit computer with the 64-bit versions of the
> .NET Frameworks installed, but it doesn't mention any settings
> that must be made (if any) to cause it to produce code for 64-bit
> apps.
>
> *TimDaniels*
>
> "Bobby Johnson" wrote:
>> Please provide a link about 'emitting 64-bit code' because this
>> sounds rather strange.
>>
>>
>> Timothy Daniels wrote:
>>> On-line lists of features for VS 2008 list the capability of
>>> emitting code for 64-bit computing if VS is installed on a
>>> 64-bit computer. Does anyone know if such installation
>>> is sufficient to cause VS to emit 64-bit code, or is there
>>> additional parameters that must be set during installation
>>> or at development time to cause VS to emit 64-bit code?
>>>
>>> *TimDaniels*
>>>
>>>

>
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

I'm sorry for the syniscism - couldn't stop myself. Once upon a time, (VS
5!) the Academic versions were limited in some ways (usually regarding
redistribution, and stuff) I don't know about the current state of affairs,
but Tech Net would be able to clear any doubts.

I would brace myself for disappointment!


Tony. . .


"Timothy Daniels" <NoSpam@SpamMeNot.com> wrote in message
news:%23qtxa8INJHA.5388@TK2MSFTNGP04.phx.gbl...
> My questions is basically whether VS will emit code that is appropriate
> for the machine on which the code is compiled, not whether VS can read
> human minds. I did leave out that the VS available to me for purchase is
> the Academic Edition of VS 2008 - which is the Professional Edition plus
> examples - which is capable of 64-bit development. I'll try the Tech Net
> fourms.
>
> *TimDaniels*
>
> "Tony Sperling" wrote:
>> As far as I'm aware, the regular release version that you buy does
>> compile to 64bit. The 'Express' versions, does not! A wild guess would be
>> that you probably may have to configure each project that you create, to
>> target the necessary libraries - it's a rare thing to see software read
>> your mind!
>>
>> Please check with the Tech Net forums for more informed answers, this is
>> primarily a 64bit OS user forum - not a developer NG!
>>
>>
>> Tony. . .
>>
>>
>> "Timothy Daniels" wrote:
>>> On-line lists of features for VS 2008 list the capability of
>>> emitting code for 64-bit computing if VS is installed on a
>>> 64-bit computer. Does anyone know if such installation
>>> is sufficient to cause VS to emit 64-bit code, or is there
>>> additional parameters that must be set during installation
>>> or at development time to cause VS to emit 64-bit code?
>>>
>>> *TimDaniels*
>>>

>>
>>

>
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

I think 'emit' may not be the best choice:


emit

One entry found.


Main Entry: emit Listen to the pronunciation of emit
<javascript:popWin('/cgi-bin/audio.pl?emit0001.wav=emit')>
Pronunciation: \e--?mit\

Function: /transitive verb/

Inflected Form(s): emit·ted; emit·ting
Etymology: Latin /emittere/ to send out, from /e-/ + /mittere/ to send
Date: 1598

1 a*:* to throw or give off or out (as light or heat) b*:* to send out
*:* eject <http://mw1.m-w.com/dictionary/eject>2 a*:* to issue with
authority ; /especially/ *:* to put (as money) into circulation
b/obsolete/ *:* publish <http://mw1.m-w.com/dictionary/publish>3*:* to
give utterance or voice to </emitted/ a groan>
--- emit·ter /noun

My experience is that compilers produce executable code. Light bulbs
emit light. Uranium emits radiations.




/

Timothy Daniels wrote:
> See "64-bit Development" on this webpage, and look at the
> Visual Studio 2008 Professional Edition column:
> http://msdn.microsoft.com/en-us/vstudio/products/cc149003.aspx .
>
> "Emit code" is what the VS compiler does. It clearly states that
> VS must run on a 64-bit computer with the 64-bit versions of the
> .NET Frameworks installed, but it doesn't mention any settings
> that must be made (if any) to cause it to produce code for 64-bit
> apps.
>
> *TimDaniels*
>
> "Bobby Johnson" wrote:
>
>> Please provide a link about 'emitting 64-bit code' because this
>> sounds rather strange.
>>
>>
>> Timothy Daniels wrote:
>>
>>> On-line lists of features for VS 2008 list the capability of
>>> emitting code for 64-bit computing if VS is installed on a
>>> 64-bit computer. Does anyone know if such installation
>>> is sufficient to cause VS to emit 64-bit code, or is there
>>> additional parameters that must be set during installation
>>> or at development time to cause VS to emit 64-bit code?
>>>
>>> *TimDaniels*
>>>
>>>
>>>

>
>
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

I do not particularly like the use of 'Emit' either- the term for what the
Compiler is doing should be 'Generate' I believe.

However, with the number of Windows Language versions in use around the
world and the spread of locations from which NG users respond from, perhaps
we should allow for people making inspired translations as they write.
'Emit', as used here, is still far better than the avarage use of language
in those Far Eastern electronics equipment manuals that we've been
accustomed to recieving along with our boxes!

;0o


Tony. . .



"Bobby Johnson" <rjohnson@aol.NOSPAM.com> wrote in message
news:ub8RqKQNJHA.1160@TK2MSFTNGP04.phx.gbl...
I think 'emit' may not be the best choice:


emit

One entry found.


Main Entry: emit Listen to the pronunciation of emit
<javascript:popWin('/cgi-bin/audio.pl?emit0001.wav=emit')>
Pronunciation: \e--?mit\

Function: /transitive verb/

Inflected Form(s): emit·ted; emit·ting
Etymology: Latin /emittere/ to send out, from /e-/ + /mittere/ to send
Date: 1598

1 a*:* to throw or give off or out (as light or heat) b*:* to send out
*:* eject <http://mw1.m-w.com/dictionary/eject>2 a*:* to issue with
authority ; /especially/ *:* to put (as money) into circulation
b/obsolete/ *:* publish <http://mw1.m-w.com/dictionary/publish>3*:* to
give utterance or voice to </emitted/ a groan>
--- emit·ter /noun

My experience is that compilers produce executable code. Light bulbs
emit light. Uranium emits radiations.




/

Timothy Daniels wrote:
> See "64-bit Development" on this webpage, and look at the
> Visual Studio 2008 Professional Edition column:
> http://msdn.microsoft.com/en-us/vstudio/products/cc149003.aspx .
>
> "Emit code" is what the VS compiler does. It clearly states that
> VS must run on a 64-bit computer with the 64-bit versions of the
> .NET Frameworks installed, but it doesn't mention any settings
> that must be made (if any) to cause it to produce code for 64-bit
> apps.
>
> *TimDaniels*
>
> "Bobby Johnson" wrote:
>
>> Please provide a link about 'emitting 64-bit code' because this
>> sounds rather strange.
>>
>>
>> Timothy Daniels wrote:
>>
>>> On-line lists of features for VS 2008 list the capability of
>>> emitting code for 64-bit computing if VS is installed on a
>>> 64-bit computer. Does anyone know if such installation
>>> is sufficient to cause VS to emit 64-bit code, or is there
>>> additional parameters that must be set during installation
>>> or at development time to cause VS to emit 64-bit code?
>>>
>>> *TimDaniels*
>>>
>>>
>>>

>
>
>





--------------------------------------------------------------------------------


>I think 'emit' may not be the best choice:
>
> emit
> One entry found.
>
>
>
>
>
> Main Entry: emit
> Pronunciation: \e-'mit\
>
>
> Function: transitive verb
>
>
> Inflected Form(s): emit·ted; emit·ting
> Etymology: Latin emittere to send out, from e- + mittere to send
> Date: 1598
> 1 a: to throw or give off or out (as light or heat) b: to send out :
> eject2 a: to issue with authority ; especially : to put (as money) into
> circulation bobsolete : publish3: to give utterance or voice to <emitted a
> groan>
> - emit·ter noun
>
> My experience is that compilers produce executable code. Light bulbs emit
> light. Uranium emits radiations.
>
>
>
>
>
>
> Timothy Daniels wrote:
> See "64-bit Development" on this webpage, and look at the
> Visual Studio 2008 Professional Edition column:
> http://msdn.microsoft.com/en-us/vstudio/products/cc149003.aspx .
>
> "Emit code" is what the VS compiler does. It clearly states that
> VS must run on a 64-bit computer with the 64-bit versions of the
> .NET Frameworks installed, but it doesn't mention any settings
> that must be made (if any) to cause it to produce code for 64-bit
> apps.
>
> *TimDaniels*
>
> "Bobby Johnson" wrote:
> Please provide a link about 'emitting 64-bit code' because this
> sounds rather strange.
>
>
> Timothy Daniels wrote:
> On-line lists of features for VS 2008 list the capability of
> emitting code for 64-bit computing if VS is installed on a
> 64-bit computer. Does anyone know if such installation
> is sufficient to cause VS to emit 64-bit code, or is there
> additional parameters that must be set during installation
> or at development time to cause VS to emit 64-bit code?
>
> *TimDaniels*
>
>
>
>
>
>
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

Timothy Daniels wrote:
> My questions is basically whether VS will emit code that is
> appropriate for the machine on which the code is compiled, not
> whether VS can read human minds. I did leave out that the VS
> available to me for purchase is the Academic Edition of VS 2008 -
> which is the Professional Edition plus examples - which is capable
> of 64-bit development. I'll try the Tech Net fourms.
>


It doesn't matter what machine you run the compiler on. You select the
target in the project settings, and compile for that.

On the other hand, to be able to run the program you must have the
proper environment.


Bo Persson
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

He didn't choose it. The term has been used technically in the context of compilers for as long as I've been in the game which (heaven help me) is nearly 40 years.
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

I know I'm a relative youngster since I didn't take Comp Sci until 1985,
but that term was not in use at the University of Nebraska-Lincoln while
I was going through.

Doug Forster wrote:
> He didn't choose it. The term has been used technically in the context
> of compilers for as long as I've been in the game which (heaven help
> me) is nearly 40 years.
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

"Bo Persson" skrev:
> It doesn't matter what machine you run the compiler on. You select the target
> in the project settings, and compile for that.
>
> On the other hand, to be able to run the program you must have the proper
> environment.
>
>
> Bo Persson


Thanks for confirming.

*TimDaniels*
 
Re: setup for Visual Studio 2008 Pro Ed. on 64-bit computer

"Tony Sperling" wrote:
> I do not particularly like the use of 'Emit' either- the term for what the
> Compiler is doing should be 'Generate' I believe.



"Emit" sounds strange to my ears as well, but that is what
the .NET compilers do. Here is an example of the use of "emit",
from http://www.developer.com/lang/jscript/print.php/944871 :

"Unlike traditional compilers, which emit code that a system's processor
can directly execute, .NET compilers - including the JScript .NET compiler -
emit code in another language called Microsoft Intermediate Language
(MSIL, or simply IL)."

*TimDaniels*
 
Back
Top