|
Not bored - just nonplussed. We do this the 1st way you talekd about a lot from Serviced components and it works fine.
|
|
|
|
|
How do you do component licensing in .NET - i.e. so that people must have a license file to use your control in the design environment?
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
I have installed the .NET framwework SDK. But whenever I try to manually compile code it can't find csc.exe. Is there some way to register it so i can use it right from a command prompt? I can only get it to work if i am running it from it's root directory.
Steve
McLenithan
Is Bert Evil?
|
|
|
|
|
I guess that, because you haven't installed the VS.NET IDE, you don't have the vcvars32.bat which sets all paths.
Here it is, just in case :
---- BEGINS HERE ----
@SET VSINSTALLDIR=C:\vc7\Common7\IDE
@SET VCINSTALLDIR=C:\vc7
@SET FrameworkDir=C:\WINNT\Microsoft.NET\Framework
@SET FrameworkVersion=v1.0.3705
@SET FrameworkSDKDir=C:\vc7\FrameworkSDK
@rem Root of Visual Studio common files.
@if "%VSINSTALLDIR%"=="" goto Usage
@if "%VCINSTALLDIR%"=="" set VCINSTALLDIR=%VSINSTALLDIR%
@rem
@rem Root of Visual Studio ide installed files.
@rem
@set DevEnvDir=%VSINSTALLDIR%
@rem
@rem Root of Visual C++ installed files.
@rem
@set MSVCDir=%VCINSTALLDIR%\VC7
@rem
@echo Setting environment for using Microsoft Visual Studio .NET tools.
@echo (If you also have Visual C++ 6.0 installed and wish to use its tools
@echo from the command line, run vcvars32.bat for Visual C++ 6.0.)
@rem
@REM %VCINSTALLDIR%\Common7\Tools dir is added only for real setup.
@set PATH=%DevEnvDir%;%MSVCDir%\BIN;%VCINSTALLDIR%\Common7\Tools;%VCINSTALLDIR%\Common7\Tools\bin\prerelease;%VCINSTALLDIR%\Common7\Tools\bin;%FrameworkSDKDir%\bin;%FrameworkDir%\%FrameworkVersion%;%PATH%;
@set INCLUDE=%MSVCDir%\ATLMFC\INCLUDE;%MSVCDir%\INCLUDE;%MSVCDir%\PlatformSDK\include\prerelease;%MSVCDir%\PlatformSDK\include;%FrameworkSDKDir%\include;%INCLUDE%
@set LIB=%MSVCDir%\ATLMFC\LIB;%MSVCDir%\LIB;%MSVCDir%\PlatformSDK\lib\prerelease;%MSVCDir%\PlatformSDK\lib;%FrameworkSDKDir%\lib;%LIB%
@goto end
:Usage
@echo. VSINSTALLDIR variable is not set.
@echo.
@echo SYNTAX: %0
@goto end
:end
---- ENDS HERE ----
Replace the FrameworkVersion variable with the appropriate value. Since you seem not to have the VS.NET IDE, in fact only a fraction of those variables are useful. For csc.exe, what's important to have is the PATH variable.
My recommendation is to directly add the appropriate paths in your user environment variables, from the OS config panel.
|
|
|
|
|
That is the weird thing I DID install VS.net. I don't know why it isn't working. But I will add that path variable like you suggested.
Thanks
Steve
McLenithan
Is Bert Evil?
|
|
|
|
|
1. It doesnt add the path by default (god knows why).
2. Windows operating systems still needs a reboot for PATH variables to take effect (no-one knows why).
Hey leppie! Your "proof" seems brilliant and absurd at the same time. - Vikram Punathambekar 28 Apr '03
|
|
|
|
|
The best way is to use the "Visual Studio.NET (2003) Command Prompt" in your Tools menu under "Start/Program Files/Visual Studio.NET". This will launch a command (cmd) window with all of the paths set etc. The nice thing is that they only exist for that session so you don't end up with masses of system or user path settings which is a bit Win95ey!!! (IMHO!!) 
Shaun
|
|
|
|
|
leppie wrote:
It doesnt add the path by default (god knows why).
The old VS6 installation used to ask you if you wanted this to happen. I'm surprised they took this out in VS7 (I don't remember seeing that option in the install either...). But there's always the "Visual Studio Command Prompt" shortcut that VS.NET creates. I've put it on my shortcut bar for easy use 
As for the .NET FrameworkSDK, it provides a 'corvars.bat' in the FrameworkSDK/bin directory that sets PATH to allow for easy usage of the compilers and tools that come with the SDK.
leppie wrote:
Windows operating systems still needs a reboot for PATH variables to take effect (no-one knows why).
The NT line doesn't require an OS reboot under these circumstances. When a new process starts, it gets its own copy of the current environment. This means that just the process will need to be restarted - not the whole OS. For instance, if you change PATH, all command lines you currently have open will continue to use the old PATH, but new ones you open will use the new PATH. You can force explorer to recognize new environment variable changes be using TaskManager to shut it down and restart it.
--
Russell Morris
"Have you gone mad Frink? Put down that science pole!"
|
|
|
|
|
Hi Steve,
You can use Start -> Programs -> Microsoft Visual Studio .NET -> Visual Studio .NET Command Prompt
(That will set all path variables necessary for .NET applications). Perhaps I think this is a batch file. We can copy necessary values and put them onto System Path as well. I have'nt tried that anyway, but should work too.
Deepak Kumar Vasudevan
http://deepak.portland.co.uk/
|
|
|
|
|
hi all,
the question is :
"Is there any support in .net to capture the ethernet packet moving on the network?"
regards
|
|
|
|
|
Somewere on this very site - name eludes me though
|
|
|
|
|
In my program ,I create a new Bitmap use
Bitmap bmp = new Bitmap(200,200);
and I use the GetPixel() method to get the color info.
the result is [Color A = 0 R = 0 B = 0 G = 0]
and then I save it use the bmp.Save("C:\\ss.bmp",ImageFormat.Bmp)
but when I reload it Use the Image.FromFile()
I found that the color change to
[Color A = 255 R = 0 B = 0 G = 0]
how can I resolve this problem?
|
|
|
|
|
I'm not sure, whether bmp file format does support alpha channel...
Try using other ImageFormat (maybe Png format can be better)
i'm only pointer to myself
|
|
|
|
|
Hi folks,
I'm working on a project using both clr and non clr-Modules. I try to load a C#-assembly dxnamically from a c++Module translated with the clr option. For that I'm using the .Net-Assembly class (System.Reflection.Assembly). In some cases I cannot call the function I'd like to. That depends on wheter some Objects are instantiated whithin it or not.
Here the code of the function I try to call via Reflection:
This works :
/////////////////////////
public void Init()
{
//Doc.Document doc = new Doc.Document
String txt = "hello";
}
/////////////////////////
this doesn't
/////////////////////////
public void Init()
{
Doc.Document doc = new Doc.Document;
String txt = "hello";
}
/////////////////////////
In case the critical line is there, I cannot even debug into the function, making it hard to find the error. Any Ideas ?
|
|
|
|
|
You're right, but I just wrote it down wrong from my memory, so the paranthesises are not the problem. The assemblies/modules all compile properly, so it's not a syntactical error. The assemblies/modules just do not work with each other. pitty
|
|
|
|
|
You're right, but I just wrote it down wrong from my memory, so the paranthesises are not the problem. The modules all compile properly, so it's not a syntactical error. The modules just do /do not work with each other depending on the code in the function called across the modules. pitty
|
|
|
|
|
How can I start a process under a profile different thant the one logged in? I know you can use the 'runas' utility, but there's no parameter for the password. I suppose I could launch 'runas' via Process.Start, redirect it's standard input, then send the password myself, but isn't there an easier way?
Thanks in advance.
Kyosa Jamie Nordmeyer - Cho Dan
Portland, Oregon, USA
|
|
|
|
|
The assemblies in the .NET Framework includes the metadata information with the assembly files and so no longer the component information is stored in the Registry.
So Is the Registry used only for application specific settings? But for even this situation we can use the configuration files (.config) or XML (new craze)
So what's the future of Registry in the .NET world? What I am missing?
Don't ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) and drive.
|
|
|
|
|
The new OS in development at Microsoft does not have a registry, it is all database driven!.
No I am not talking about server 2003, I think the codename is sledgehammer or something like that.
So the answer to your question is it is going to disappear as we know it.
|
|
|
|
|
Is there a way in the framework to search for a string/phrase inside of a file on the filesystem. I need similar functionality to Windows Search. I was going to write a class to read file streams and search that way, but I figured that if the framework provided that functionality, why reinvent the wheel? So if you know of a function call inside of the framework that can accomplish this I would appreciate it.
Scott
|
|
|
|
|
Does anyone know where the documentation is for this? I have looked on the Internet, MS, Rotor, MSDN, etc. with no luck. Any ideas??
|
|
|
|
|
Mike_V wrote:
I have looked on the Internet, MS, Rotor, MSDN, etc. with no luck. Any ideas??
I wonder why you guys are always missing the obvious. The documentation is waiting for you on your hard drive. It comes with the .NET framework SDK : <framework SDK folder> \ Tools developers guide \ docs \ Assembly Metadata Unmanaged API.doc
|
|
|
|
|
Oops!
I didn't know about this folder. It looks like there are some interesting things here...
Thanks!
|
|
|
|
|
Ya'll listen up real good now, ya'hear?
I just spent the last 45 minutes yelling at the .NET Framework because it kept telling me that no public installer was found in my Windows Service code. Even though I had expressely coded in an installer, as per about twenty different articles instructions.
It then dawned on me; I had made the project in Visual Studio.NET 2003, but I was running INSTALLUTIL.exe from the .NET Framework v1.0 folder, not .NET Framework v1.1.
As soon as I swapped to v1.1 it worked beautifully.
I think the lesson I have learnt the most of late is; If you are going to use Visual Studio .NET 2003 then make sure all your deployment machines/servers are running the .NET Framework v1.1.
Paul Watson
Bluegrass
Cape Town, South Africa
brianwelsch wrote:
I find my day goes by more smoothly if I never question other peoples fantasies. My own disturb me enough.
|
|
|
|
|
Paul Watson wrote:
I think the lesson I have learnt the most of late is; If you are going to use Visual Studio .NET 2003 then make sure all your deployment machines/servers are running the .NET Framework v1.1
When you know that VS.NET 2003 always targets .NET 1.1 because of marketing reasons, you end up repeating for yourself that "marketing people rule developers .. marketing people rule developers ...", which shows quite well the mess in what we are now...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
