I have a dll that I created to use in all of the programs I create. I have one program that when I call a sub or function that is in the dll I can step into the dll code and look to see if I have any problems with the dll. I have another program where I cannot step into this dll. I assume this is a setting in visual studio because I can do this on two different machines. I have been unable to find the setting to turn on in the second project or the reason why this is occuring. Does anyone have any suggestions? Thanks

You have to reference the project that builds your DLL, not the DLL itself
to step through.

-cJ
"mike" <(E-Mail Removed)> wrote in message
news:7372AD2F-C715-46CD-9A61-(E-Mail Removed)...
> I have a dll that I created to use in all of the programs I create. I
have one program that when I call a sub or function that is in the dll I can
step into the dll code and look to see if I have any problems with the dll.
I have another program where I cannot step into this dll. I assume this is
a setting in visual studio because I can do this on two different machines.
I have been unable to find the setting to turn on in the second project or
the reason why this is occuring. Does anyone have any suggestions? Thanks

* "=?Utf-8?B?bWlrZQ==?=" <(E-Mail Removed)> scripsit:
> I have a dll that I created to use in all of the programs I create. I
> have one program that when I call a sub or function that is in the dll I
> can step into the dll code and look to see if I have any problems with
> the dll. I have another program where I cannot step into this dll. I
> assume this is a setting in visual studio because I can do this on two
> different machines. I have been unable to find the setting to turn on
> in the second project or the reason why this is occuring. Does anyone
> have any suggestions?

Is the DLL's source available on the 2nd computer? Are the projects
part of the same solution?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet/>

Hi Mike,

If you have the source code available for the DLL, you can do the following:

1. Open the solution for the program that calls your DLL
2. Set a breakpoint at the line of code that calls your DLL
3. Open the DLL's source file that will be called (File --> Open -->
File...)

You should then be able to run your solution, stop at your breakpoint, and
then step into the DLL. Please try these steps and let me know how it goes.

HTH,
Derrick


"mike" <(E-Mail Removed)> wrote in message
news:7372AD2F-C715-46CD-9A61-(E-Mail Removed)...
> I have a dll that I created to use in all of the programs I create. I
have one program that when I call a sub or function that is in the dll I can
step into the dll code and look to see if I have any problems with the dll.
I have another program where I cannot step into this dll. I assume this is
a setting in visual studio because I can do this on two different machines.
I have been unable to find the setting to turn on in the second project or
the reason why this is occuring. Does anyone have any suggestions? Thanks