DonB
|
| Posted: 06/05/2002, 6:04 PM |
|
I got this when I try to deploy one of the samples after specifying it to be
"C#";
Error: Unable to find C# compiler. Please specify Tools>Options>Paths>.NET
SDK
I used the path
c:\WindowsMicrosoft.NET\Framework\v1.0.3705
because that location happened to have "csc.exe" in it.
Can someone confirm this is what was intended (it works)? The Tools Options
Paths dialog just indicates the ".NET SDK", which at first consideration led
me to think I needed to point somewhere else (which did NOT work).
thanks,
don
|
|
|
 |
Sanddy
|
| Posted: 06/06/2002, 12:38 AM |
|
Looks like a typo ... this
c:\WindowsMicrosoft.NET\Framework\v1.0.3705
should be
c:\Windows\Microsoft.NET\Framework\v1.0.3705
--
Regards,
Sanddy
|
|
|
|
DonB
|
| Posted: 06/07/2002, 7:16 PM |
|
Just mistyped while writing the note. It's unclear from the documentation
what the intended patch should be. While I solved the problem I encountered
this way, I'm concerned that it was only "accidental" and I may run into
other problems later.
Perhaps the installation of CCS could find the path it needs through a peek
into the registry, so users son't have to worry about it?
don
"Sanddy" <e_sanddy@yahoo.com> wrote in message
news:adn3i8$f05$1@news.codecharge.com...
> Looks like a typo ... this
> c:\WindowsMicrosoft.NET\Framework\v1.0.3705
>
> should be
>
> c:\Windows\Microsoft.NET\Framework\v1.0.3705
>
> --
> Regards,
> Sanddy
>
>
|
|
|
|
Sanddy
|
| Posted: 06/07/2002, 9:29 PM |
|
I am not sure about other problems.. but relating to this particular
problem, I would really like CCS to stick to its current approach .. since
as you might be aware, the .NET has the capability to run side-by-side
different versions of .NET ... hence once .NET v2 is released you will be
able to run .NET v1 and v2 applications together on 1 machine!
In this scenario, it would be unwise for CCS to make pick .. since the users
choice will definitely differ and hours of time will be spent debugging :)
my 2 cents ..
Sanddy
|
|
|
|
|
