.NET 2005 [C#/VB] Throwing exceptions in a DLL

[balabaster]

Hey all, this might seem somewhat remedial but I'm unable to find any documentation on it - it pertains to throwing exceptions within a DLL.

I've written a DLL that contains a bunch of classes. One of my methods validates the contents of a file and throws any necessary exceptions based on invalid content - I'm using a standard "throw new exception..." call ...the thing is, when my code reaches the line where the exception is thrown, my Visual Studio IDE hangs up on that line instead of the external call to my validate method.

A short conceptual example to demonstrate:

MyDLL content:

Public Class FileContent
Public Function ValidateFile(ByVal FileName As String) As Boolean
    If Not System.IO.File.Exists(FileName) Then 
     Throw New IOException("File "& FileName & " doesn't exist.")
    End If
End Function
End Class
 

Second project that contains reference to DLL

Imports MyDLL
Public Module Module1
Sub Main()
    Dim oFC As New FileContent
    oFC.ValidateFile("C:\FileThatDoesntExist.txt")
End Sub
End Module
 

So my IDE is actually pulling up the VB file that contains the DLL content and highlights the line in the ValidateFile instead of just hanging on the oFC.ValidateFile method line where the exception is thrown instead of the IDE hanging on the oFC.ValidateFile line in my calling application.

If someone is using my DLL, I don't want them to have access to my code if their file doesn't validate, I just want them to have access to the any exceptions that are raised...am I expecting too much of VS 2005 or is this possible?

[Plater]

Hmm, I have done this and it worked just fine for me.
Do you have debugging information turned on for you .DLL (it's under the project settings, on what to do durring a debug/release build)

[balabaster]

Hmm, I have done this and it worked just fine for me.
Do you have debugging information turned on for you .DLL (it's under the project settings, on what to do durring a debug/release build)

Okay, under my debug settings, I've got "Enable the Visual Studio hosting process" checked and nothing else.

Rereading my original post, I'm wondering if I wasn't clear...

Did it make sense that my VS IDE was actually opening the VB file that is contained in the DLL assembly and highlighting the line:

Throw New Exception("File "& FileName & " doesn't exist.")

When in fact it should be hanging up in my external application on:

oFC.Validate("C:\FileThatDoesntExist.txt")

At which point my IDE should highlight the oFC.Validate line in the external application and the error should read: "File C:\FileThatDoesntExist.txt doesn't exist."

Not sure if that came across in my first post so I'm not sure if what you're getting me to do is what I'm actually trying to achieve...

[Plater]

Ahh, I thought it was the otherway around, that you WANTED to go into the DLL and it wasn't.
Debuging information is available for the DLL, so the IDE can navigate to the source code page.
I am about 90% certain that in an actual deployed situation, the compiler will not be able to enter into the source code because it will not exist.