'block'
Kamen Lilov
http://www.delera.com
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray
Sent: Thursday, September 08, 2005 7:10 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Circ
You cannot reference an .exe from VS.NET...but you can if compiling from the
command line using
csc.exe
Paul
--- Franklin Gray <[EMAIL PROTECTED]> wrote:
> Nevermindseems you can't reference an exe projectfor some reason I
> was thinking you could. Nevermind. I'll put it in a dll if w
> Nevermindseems you can't reference an exe projectfor
> some reason I was thinking you could. Nevermind. I'll put
> it in a dll if we need the variables in all projects.
You can, rename the .exe as a .dll (if it's a .net assembly).
FB
==
On 08/09/2005 17:10, Franklin Gray wrote:
This is a bad thing in the COM world but wondering if it's still bad in
the DotNet world (I used to know but forgot). I would like to use a Class
called Globals and put all global variables in there as shared so it will
be very very very clear as to them
Nevermindseems you can't reference an exe projectfor some reason I
was thinking you could. Nevermind. I'll put it in a dll if we need the
variables in all projects.
===
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage
This is a bad thing in the COM world but wondering if it's still bad in
the DotNet world (I used to know but forgot). I would like to use a Class
called Globals and put all global variables in there as shared so it will
be very very very clear as to them being global and can use intellsense
(no ne
