Inline
> -Original Message-
> From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Block, Jeffrey A.
> Sent: Sunday, July 13, 2003 6:29 PM
> To: [EMAIL PROTECTED]
>
> John,
>
> Are you actively using this?
Yes, although usually I trust
Shawn,
I couldn't reproduce it. I dropped a Save Dialog onto a Form and used the
following code:
MessageBox.Show(saveFileDialog1.ShowDialog(this).ToString());
which displayed 'OK' unless I pressed the cancel button in which case it
displayed 'Cancel'. The value of the OverwritePrompt didn't hav
I got no response on this post at dotnet-winforms... thought I'd escalate it here,
hoping somebody can confirm this as a bug.
Alternatively, if you try to repro and can't, please let me know that too. It may be
a strange symptom of some obscure shell setting I've got configured, or something.
Please forgive me if I am wrong:
VB6 had conditional compilation similar to the #if #end if in C/C++/C#.
Did that make it into VB.NET and if it did, can you use it in the
identical way to the example given by Stefan? I didn't notice in the
posts any refernce to using the feature in the VB.NET ver
Mathhew,
It seems you're right... The VB.NET compiler does include unused references.
I'm afraid the only option you have here is invoking the compiler from the
command line and omit the unneeded references.
Regards,
Stefan
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL
Stefan,
Touché! I humbly acknowledge the vast superiority of C# on this feature. :-)
Unfortunately, the VB compiler (which I am constrained to use) does not share the
ability to remove unused assembly references. Is there any way (or possibly an add-in)
that would allow VB to behave the same wa
