Do you have a short but complete example which
demonstrates theproblem? It sounds very odd to me. Are you referencing
any assembliesother than the "built-in" ones?
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too
.
I am using the following "built-ins" across various
classes:
Microsoft.Win32
System
System.Collections
System.ComponentModel
System.Data
System.Diagnostics
System.Drawing
System.IO
System.Runtime.InteropServices
System.Security
System.Security.Permissions
System.Text
System.Text.RegularExpressions
System.Threading
System.Windows.Forms
System.Xml
It just occurred to me that one of my classes makes a
call to an unmanaged Windows API that is not available in
the .Net Framework - could this be a factor?
Here is the declaration:
----------------------------------------------------------
[DllImport("kernel32.dll",CharSet=CharSet.Auto,
SetLastError=true)]
[return:MarshalAs(UnmanagedType.Bool)]
private static extern bool SetEnvironmentVariable(string
lpName, string lpValue);
----------------------------------------------------------
I compile with the following command line:
csc /out:myapp.exe /win32icon:myicon.ico /target:winexe
*.cs
The .cs files in the current directory include all forms
and classes for the app as well as the AssemblyInfo.cs
created by the IDE.
I can't really give you a complete example that would
also be short! Suffice to say though that apart from that
API call everything else is bog standard - no funny
stuff, just calls to Framework objects. My main form
uses a TreeView control, a DataGrid, and a couple of
buttons - pretty simple. It parses some XML and
populates the TreeView with node objects of my own class
that inherits from TreeNode. Once the tree is built you
can launch command-line sessions based on parameters
supplied by the selected tree node.