yep, this works @ run time. How does this work @ debug
my project structure is
\solution\webserviceprojec
\solution\assemblyprojec
files are built to \solution\build (this is common to both projects, but only the assembly delivers files to here
I need to step through both the webservice and the referenced assembly (currently as a project reference
------------------------------------------------------------------------------------------------------------
Neil Macdonal
Senior Software Enginee
IntelliWhere Product Development Centr
Intergraph Corporation (NASDAQ: INGR
Intergraph Mapping and Geospatial Solution
Level 3, 299 Coronation Drive, Milton QLD Australia
Hi Neil,
Please feel free to correct me if I have misunderstood this. Based on my
understanding, you are working with a web serivce project, and its asmx
file should be in a virtual diretory, its assembly file (dll) should be in
a "bin" folder. However, from your description, they are in
"\solution\build". Can you explain more on this?
Regards,
Luke
Microsoft Online Support

Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Neil Macdonald [Intergraph] - 08 Jun 2004 04:51 GMT
- I have one solution containing both the DLL/Assembly and the WebServic
- When I call GetExecutingAssembly() in the DLL it gives me the ASP.NET temp directory not the directory of where the dll i
- Both project outputs are set t \Solution\Buil
- I need to load an xml .config file in the DLL on initialization this currently is in the \build directory, along with the compiled project output (dll
- I want to be able to step through the code in both the webservice and DLL and return the right results
I am sure it is a simple solution
------------------------------------------------------------------------------------------------------------
Neil Macdonal
Senior Software Enginee
IntelliWhere Product Development Centr
Intergraph Corporation (NASDAQ: INGR
Intergraph Mapping and Geospatial Solution
Level 3, 299 Coronation Drive, Milton QLD Australia
[MSFT] - 08 Jun 2004 08:01 GMT
Hi Neil,
If you just want get the DLL's path, you may try following code in the
Class library:
System.Reflection.Assembly.GetAssembly( this.GetType() ).CodeBase.ToString()
Luke
Microsoft Online Support

Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)