Problem viewing some source files
Brian Donahue
Posts: 6,590 Bronze 1
Hi Chris,
Have you tried giving read/write permissions to everyone in the source
code folders for the dlls?
This has worked in the past although I still can't find a possible
explanation for it.
Regards,
Brian Donahue
Red Gate Technical Support
"Chris Powell" <cpowell@spanpro.com> wrote in message
news:vwq6SQvaEHA.3124@server53...
> Here's my problem:
> I have a VB.Net exe that has a group of VB.net Dlls that it uses to
> do it's tasks. These were all compiled debug. Also they are strong named.
I
> never recompile the Exe but as I make changes to the Dlls I make changes
to
> them and then modify the Exes config to redirect the binding of the dlls
to
> the new dlls (Each version set of dlls goes in its own directory)
>
> Example of directory structure:
> <===============================>
> Base Dir
> 2.95.1654.17659
> 2.96.1654.17659
> <===============================>
>
> I can profile this fine and get procedure timings and 100 worst functions
> and the like, but can only get source to show up for the exe. I copied the
> *.pbd files for each exe/dll next to the appropriate item, I then tried
> copying all the *.pdb files next to the exe still no dice. Also when I'm
> looking at one of the subs or modules from these other dlls the
view:Locate
> source control is grayed out. Is there any way for me to look at line
timing
> in these dlls.
> Chris
>
>
Have you tried giving read/write permissions to everyone in the source
code folders for the dlls?
This has worked in the past although I still can't find a possible
explanation for it.
Regards,
Brian Donahue
Red Gate Technical Support
"Chris Powell" <cpowell@spanpro.com> wrote in message
news:vwq6SQvaEHA.3124@server53...
> Here's my problem:
> I have a VB.Net exe that has a group of VB.net Dlls that it uses to
> do it's tasks. These were all compiled debug. Also they are strong named.
I
> never recompile the Exe but as I make changes to the Dlls I make changes
to
> them and then modify the Exes config to redirect the binding of the dlls
to
> the new dlls (Each version set of dlls goes in its own directory)
>
> Example of directory structure:
> <===============================>
> Base Dir
> 2.95.1654.17659
> 2.96.1654.17659
> <===============================>
>
> I can profile this fine and get procedure timings and 100 worst functions
> and the like, but can only get source to show up for the exe. I copied the
> *.pbd files for each exe/dll next to the appropriate item, I then tried
> copying all the *.pdb files next to the exe still no dice. Also when I'm
> looking at one of the subs or modules from these other dlls the
view:Locate
> source control is grayed out. Is there any way for me to look at line
timing
> in these dlls.
> Chris
>
>
This discussion has been closed.
