Hi,
I want to generate a dll for x64. In the project, I specify the
platform target x64 but VS2005 use the win32 framework. Here is the
warnings that I get :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc. exe /noconfig
/nowarn:1701,1702 /platform:x64 /errorreport:prompt
/baseaddress:285212672 /define:TRACE;DEBUG
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Drawing.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Windows.Forms.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Xml.dll
/debug+ /debug:full /out:obj\x64\Debug\CFGDistributeur.dll ...
warning CS1607: Assembly generation -- Referenced assembly
'System.Data.dll' targets a different processor
warning CS1607: Assembly generation -- Referenced assembly
'mscorlib.dll' targets a different processor
So I want to know how the specify in VS2005 the use the Framework64
(x64) and not use the Framework (win32).
Thanks,
Eric 5 17622
"Eric" <cl**********@gmail.comwrote in message
news:11**********************@s80g2000cwa.googlegr oups.com...
Hi,
I want to generate a dll for x64. In the project, I specify the
platform target x64 but VS2005 use the win32 framework. Here is the
warnings that I get :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc. exe /noconfig
/nowarn:1701,1702 /platform:x64 /errorreport:prompt
/baseaddress:285212672 /define:TRACE;DEBUG
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Drawing.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Windows.Forms.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Xml.dll
/debug+ /debug:full /out:obj\x64\Debug\CFGDistributeur.dll ...
warning CS1607: Assembly generation -- Referenced assembly
'System.Data.dll' targets a different processor
warning CS1607: Assembly generation -- Referenced assembly
'mscorlib.dll' targets a different processor
So I want to know how the specify in VS2005 the use the Framework64
(x64) and not use the Framework (win32).
Thanks,
Eric
Well there are two issues here, I hoped SP1 would have solved, but it's not:
1. VS is using csc from the 32bit framework.
2. VS references the assemblies from the 32 bit framework and some assemblies are built as
X86.
Now this is no big deal (unless these warnings get you nervous :))) , at run-time the
program will correctly load the 64 bit CLR and the correct 64bit FCL assemblies.
Willy.
Willy Denoyette [MVP] wrote:
"Eric" <cl**********@gmail.comwrote in message
news:11**********************@s80g2000cwa.googlegr oups.com...
Hi,
I want to generate a dll for x64. In the project, I specify the
platform target x64 but VS2005 use the win32 framework. Here is the
warnings that I get :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc. exe /noconfig
/nowarn:1701,1702 /platform:x64 /errorreport:prompt
/baseaddress:285212672 /define:TRACE;DEBUG
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Drawing.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Windows.Forms.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Xml.dll
/debug+ /debug:full /out:obj\x64\Debug\CFGDistributeur.dll ...
warning CS1607: Assembly generation -- Referenced assembly
'System.Data.dll' targets a different processor
warning CS1607: Assembly generation -- Referenced assembly
'mscorlib.dll' targets a different processor
So I want to know how the specify in VS2005 the use the Framework64
(x64) and not use the Framework (win32).
Thanks,
Eric
Well there are two issues here, I hoped SP1 would have solved, but it's not:
1. VS is using csc from the 32bit framework.
2. VS references the assemblies from the 32 bit framework and some assemblies are built as
X86.
Now this is no big deal (unless these warnings get you nervous :))) , at run-time the
program will correctly load the 64 bit CLR and the correct 64bit FCL assemblies.
Willy.
Is there possible to specify VS2005 to use csc from the 64bit
framework? How?
I have a C++ application (64-bits) that load C# applet (need to be
64-bits). My application wasn't able to load the applet. The solution
that I found, is the compile manually from the command line the applet
with the csc.exe and system dll from the 64-bits framework.
Regards,
Eric
"Eric" <cl**********@gmail.comwrote in message
news:11**********************@q40g2000cwq.googlegr oups.com...
>
Willy Denoyette [MVP] wrote:
>"Eric" <cl**********@gmail.comwrote in message news:11**********************@s80g2000cwa.googleg roups.com...
Hi,
I want to generate a dll for x64. In the project, I specify the
platform target x64 but VS2005 use the win32 framework. Here is the
warnings that I get :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc. exe /noconfig
/nowarn:1701,1702 /platform:x64 /errorreport:prompt
/baseaddress:285212672 /define:TRACE;DEBUG
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Drawing.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Windows.Forms.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Xml.dll
/debug+ /debug:full /out:obj\x64\Debug\CFGDistributeur.dll ...
warning CS1607: Assembly generation -- Referenced assembly
'System.Data.dll' targets a different processor
warning CS1607: Assembly generation -- Referenced assembly
'mscorlib.dll' targets a different processor
So I want to know how the specify in VS2005 the use the Framework64
(x64) and not use the Framework (win32).
Thanks,
Eric Well there are two issues here, I hoped SP1 would have solved, but it's not: 1. VS is using csc from the 32bit framework. 2. VS references the assemblies from the 32 bit framework and some assemblies are built as X86. Now this is no big deal (unless these warnings get you nervous :))) , at run-time the program will correctly load the 64 bit CLR and the correct 64bit FCL assemblies.
Willy.
Is there possible to specify VS2005 to use csc from the 64bit
framework? How?
No that I know.
I have a C++ application (64-bits) that load C# applet (need to be
64-bits). My application wasn't able to load the applet. The solution
that I found, is the compile manually from the command line the applet
with the csc.exe and system dll from the 64-bits framework.
This shouldn't be a problem, if you did compile from VS with the "platform" set to "x64",
you can safely ignore the warnings, the resultant DLL should have the correct PE and CLR
header.
What error message did you get when loading the applet?
Willy.
Willy Denoyette [MVP] wrote:
"Eric" <cl**********@gmail.comwrote in message
news:11**********************@q40g2000cwq.googlegr oups.com...
Willy Denoyette [MVP] wrote:
"Eric" <cl**********@gmail.comwrote in message
news:11**********************@s80g2000cwa.googlegr oups.com...
Hi,
I want to generate a dll for x64. In the project, I specify the
platform target x64 but VS2005 use the win32 framework. Here is the
warnings that I get :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc. exe /noconfig
/nowarn:1701,1702 /platform:x64 /errorreport:prompt
/baseaddress:285212672 /define:TRACE;DEBUG
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Drawing.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Windows.Forms.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Xml.dll
/debug+ /debug:full /out:obj\x64\Debug\CFGDistributeur.dll ...
warning CS1607: Assembly generation -- Referenced assembly
'System.Data.dll' targets a different processor
warning CS1607: Assembly generation -- Referenced assembly
'mscorlib.dll' targets a different processor
So I want to know how the specify in VS2005 the use the Framework64
(x64) and not use the Framework (win32).
Thanks,
Eric
Well there are two issues here, I hoped SP1 would have solved, but it's not:
1. VS is using csc from the 32bit framework.
2. VS references the assemblies from the 32 bit framework and some assemblies are built
as
X86.
Now this is no big deal (unless these warnings get you nervous :))) , at run-time the
program will correctly load the 64 bit CLR and the correct 64bit FCL assemblies.
Willy.
Is there possible to specify VS2005 to use csc from the 64bit
framework? How?
No that I know.
I have a C++ application (64-bits) that load C# applet (need to be
64-bits). My application wasn't able to load the applet. The solution
that I found, is the compile manually from the command line the applet
with the csc.exe and system dll from the 64-bits framework.
This shouldn't be a problem, if you did compile from VS with the "platform" set to "x64",
you can safely ignore the warnings, the resultant DLL should have the correct PE and CLR
header.
What error message did you get when loading the applet?
Willy.
I did what you said. I didn't receive any error message. In run-time,
the applet just didn't load.
The first thing that I do, was use the application RegAsm.exe from the
framework64. After that, the applet didn't load again. So I recompile
with the csc.exe and system.dll, system.data.dll ... from the
framework64 (manually from the command line) and this time the applet
load.
Regards,
Eric
Eric
"Eric" <cl**********@gmail.comwrote in message
news:11**********************@11g2000cwr.googlegro ups.com...
>
Willy Denoyette [MVP] wrote:
>"Eric" <cl**********@gmail.comwrote in message news:11**********************@q40g2000cwq.googleg roups.com...
>
Willy Denoyette [MVP] wrote: "Eric" <cl**********@gmail.comwrote in message news:11**********************@s80g2000cwa.googleg roups.com...
Hi,
I want to generate a dll for x64. In the project, I specify the
platform target x64 but VS2005 use the win32 framework. Here is the
warnings that I get :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc. exe /noconfig
/nowarn:1701,1702 /platform:x64 /errorreport:prompt
/baseaddress:285212672 /define:TRACE;DEBUG
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Drawing.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Windows.Forms.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0. 50727\System.Xml.dll
/debug+ /debug:full /out:obj\x64\Debug\CFGDistributeur.dll ...
warning CS1607: Assembly generation -- Referenced assembly
'System.Data.dll' targets a different processor
warning CS1607: Assembly generation -- Referenced assembly
'mscorlib.dll' targets a different processor
So I want to know how the specify in VS2005 the use the Framework64
(x64) and not use the Framework (win32).
Thanks,
Eric
Well there are two issues here, I hoped SP1 would have solved, but it's not: 1. VS is using csc from the 32bit framework. 2. VS references the assemblies from the 32 bit framework and some assemblies are built as X86. Now this is no big deal (unless these warnings get you nervous :))) , at run-time the program will correctly load the 64 bit CLR and the correct 64bit FCL assemblies.
Willy.
Is there possible to specify VS2005 to use csc from the 64bit
framework? How?
No that I know.
I have a C++ application (64-bits) that load C# applet (need to be
64-bits). My application wasn't able to load the applet. The solution
that I found, is the compile manually from the command line the applet
with the csc.exe and system dll from the 64-bits framework. This shouldn't be a problem, if you did compile from VS with the "platform" set to "x64", you can safely ignore the warnings, the resultant DLL should have the correct PE and CLR header. What error message did you get when loading the applet?
Willy.
I did what you said. I didn't receive any error message. In run-time,
the applet just didn't load.
The first thing that I do, was use the application RegAsm.exe from the
framework64. After that, the applet didn't load again. So I recompile
with the csc.exe and system.dll, system.data.dll ... from the
framework64 (manually from the command line) and this time the applet
load.
Regards,
Eric
Eric
Wait a minute now I get it, this applet is a COM object (at least for the native client),
you need to "regasm" this dll using the 64 bit version of regasm, this is the cullprit, not
the compiler. You can do this in VS by specifying a post build event that initiates
regasm.exe from ?:\Windows\Microsoft.NET\Framework64\v2.0.50727.
Willy. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Brandon Bray [MSFT] |
last post by:
Shortly, the Visual C++ Tools Refresh will be available on the MSDN Visual
C++ devcenter. You will need to have installed the Visual Studio 2005 Beta
first. <http://msdn.microsoft.com/visualc>
I...
|
by: Tom McL. |
last post by:
I'm trying to move a program that was designed using Visual Studio 2003 and
(Visual Basic) into Visual Studio 2005. When it runs I get the following
warning in the
Error List Window and I'm not...
|
by: Riaan |
last post by:
I am compiling my app (including CODEBASE database headers) but as soon as i
compile it gives me the following errors :
c:\Program Files\Microsoft Visual Studio\VC98\Include\UTILITY(81) : warning...
|
by: Michel |
last post by:
In VC++ from Visual Studio 2005 the following occurs: If I try to compile
anyting, even a newly created empty MFC application with 1 empty dialog, I
get the following 2 errors:
Compiling......
|
by: Nathan Sokalski |
last post by:
I am an ASP.NET developer, and Visual Studio 2005 seems to have stopped
declaring the controls that I add in the *.designer.vb files, therefore
forcing me to manually add them before I can use them...
|
by: Nathan Sokalski |
last post by:
Visual Studio 2005 recently stopped generating the *.designer.vb files for
my *.aspx and *.ascx files. I am using Service Pack 1, and do not believe I
did anything differently than normal prior to...
|
by: Nathan Sokalski |
last post by:
Visual Studio 2005 unexpectedly stopped generating the *.designer.vb files
for *.aspx and *.ascx files. After a few days of frustration trying to fix
this, I noticed that it had the following...
|
by: marathoner |
last post by:
I am currently migrating my Visual C++ 6.0 applications to Visual Studio
2005. I am getting compiler errors involving the VS2005's platform SDK.
When I removed directory references to that SDK,...
|
by: jon2211 |
last post by:
I tried to compile some code with #include <shellapi.h. I am
linking shell32.lib. I am not trying to use ShellExecute() but right
now just getting the code to compile with the header file an...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
| |