N
noisefree
Hello,
I have a problem on an application I am developing:
This C# Windows Application calls a C# Web Service, which it uses the
SourceSafeTypeLib DLL to interact with Visual Source Safe 6.
The problem comes out when I call the VSS method "Get(ref string Local,
int flags)", which should get a VSS file and save it to disk.
I pass "E:\max\tmp\vss\AssemblyInfo.cs" as the Local path string, but
the program exit with the error:
"System.Runtime.InteropServices.COMException (0x8004D84B): Access to
file "d:\windows\system32\inetsrv\AssemblyInfo.cs" denied".
As you can see this is NOT the path I gave to the program (why win2K3
is changing it?)
It used to work just fine on Windows XP, that's why I'm pretty sure
it's not an application problem.
Unfortunately a few days ago I had my laptop re-installed w/Win2003,
and since then it won't work anymore
So after some research I've found out that it should depends on the way
Win2003 handles access security..
If it can help: the VSS DB is on another machine which I map as share
and access it with the proper authenticated domain user (I repeat: on
WinXP it worked just fine...)
Any guess would be appreciated.
thank you
I have a problem on an application I am developing:
This C# Windows Application calls a C# Web Service, which it uses the
SourceSafeTypeLib DLL to interact with Visual Source Safe 6.
The problem comes out when I call the VSS method "Get(ref string Local,
int flags)", which should get a VSS file and save it to disk.
I pass "E:\max\tmp\vss\AssemblyInfo.cs" as the Local path string, but
the program exit with the error:
"System.Runtime.InteropServices.COMException (0x8004D84B): Access to
file "d:\windows\system32\inetsrv\AssemblyInfo.cs" denied".
As you can see this is NOT the path I gave to the program (why win2K3
is changing it?)
It used to work just fine on Windows XP, that's why I'm pretty sure
it's not an application problem.
Unfortunately a few days ago I had my laptop re-installed w/Win2003,
and since then it won't work anymore
So after some research I've found out that it should depends on the way
Win2003 handles access security..
If it can help: the VSS DB is on another machine which I map as share
and access it with the proper authenticated domain user (I repeat: on
WinXP it worked just fine...)
Any guess would be appreciated.
thank you