Re: VB.NET compiler does not find type error at compiletime

Tech-Archive recommends: Fix windows errors by optimizing your registry

This is just one more example of why you are actually better off using
copy/paste to convert VB 6 code. More VB 6 code will actually convert
better without the project converter.

Mike.


"PitG" <PitG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A42E64E-CF8D-4AAC-8AE0-D28FBB2AAC6E@xxxxxxxxxxxxxxxx
Hi Tom,

you are right - i did not set the Option Strict ON for this simple example
code.

BUT: the Project itselft was worked on with Option Strict ON set at
project
level and there is no message! (i just rechecked)

The reason for not finding the bugs is a automatically (by the converter)
placed statement on each code file of:
Option Strict Off

which overrides the central settings of Option Strict ON.

So thanks - i could go and "hunting bugs"

--
PG


"Tom Shelton" wrote:

On May 5, 3:27 am, PitG <P...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Here the facts as code sample:

Public Class Class1
Sub ABC(ByVal item As IUnit)
End Sub
End Class

Public Interface IUnit ' or any other Interface
ReadOnly Property Heureka() As Activator
ReadOnly Property Reference() As String
ReadOnly Property Name() As String
End Interface

This client is calling ABC the wrong way!
Public Class Class2
Sub test()
Dim C1 As New Class1
C1.ABC("aberhallo")
End Sub
End Class

the .NET 2.0 Compiler does not see this type error at compiletime but
at
runtime!
We tried sharpening the compiler with all potential options, but no
success.

(this kind of bug is produced many times by the VB6 to .NET migration
tool -
which is a serious issue if you have about 700 classes to check ...)

Does someone know what went wrong here - or even better to get around
this?

--
PG

Do you have option strict turned on? My guess is no.

--
Tom Shelton






.

Relevant Pages

  • RE: passing enum value as an argument
    ... > hours after your only previous reference to Option Strict? ... indeed you would have an Enum, and you WOULD have to use the same type on the ... the compiler would force you to ... >> Public sub New ...
    (microsoft.public.dotnet.general)
  • Re: VB.NET compiler does not find type error at compiletime
    ... the Project itselft was worked on with Option Strict ON set at project ... ReadOnly Property Heureka() As Activator ... We tried sharpening the compiler with all potential options, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: knowing the interfaces that an object implements
    ... I wonder why Option Strict is not on by default. ... >> If the connection variable is declared as Object the VB compiler ... >> unfortunately does not complain even with Option Explicit on. ... > Sub Main ...
    (microsoft.public.dotnet.framework)
  • Keyboard Loops
    ... With "Option Strict On" you are protected from most mistakes. ... sub BeepStartUp() ... ByVal userdata As Integer, _ ... Dim cmsg As TChannelMessage ...
    (microsoft.public.dotnet.languages.vb)
  • Re: My FIRST Class!! But it doesnt work as expected - please HELP!
    ... i code always with option strict on ... Public Sub New ... Randomize() ... Public Sub Roll() ...
    (microsoft.public.dotnet.languages.vb)