Posted By: izyani | Dec 17th, 2008 @ 5:13 PM
page 1 of 1
Comments: 1 | Views: 1619
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}

I currently done with my programming for the CSP. The problem that I’m having is, I have the different result whenever I run the CSP program. FYI, currently I have 2 type of CSP dll, a.dll already been signed by Microsoft where b.dll is the one that I develop(still in the development stage).

 

Run in Vista Ultimate/Win XP SP3.

 

Replace the latest advapi32.dll(from one of the sources from Internet)

1.       Place the a.dll and testcsp.exe to c:\windows\system32

2.       Run command : regsvr32    a.dll  à result FAIL

3.       Run command : cspSign c   a.dll à result PASS

4.       Run command : regsvr32   a.dll à result FAIL

5.       Run testcsp.exe   à result PASS

Question : Is the result PASS because the a.dll already been sent to Microsoft for signing?

 

Replace the latest advapi32.dll(from one of the sources from Internet)

1.       Place the b.dll and testcsp.exe to c:\windows\system32

2.       Run command : regsvr32    b.dll  à result FAIL

3.       Run command : cspSign c   b.dll à result PASS

4.       Run command : regsvr32   b.dll à result FAIL

5.       Run testcsp.exe   à result FAIL

Question : Is the result FAIL because the b.dll is not been signing?

 

 

Use the original advapi32.dll

1.       Place the b.dll and testcsp.exe to c:\windows\system32

2.       Run command : regsvr32    b.dll  à result FAIL

3.       Run command : cspSign c   b.dll à result PASS

4.       Run command : regsvr32   b.dll à result FAIL

5.       Run testcsp.exe   à result FAIL

Question : Is the result FAIL because I didn’t replace the advapi32.dll?

 

Run XP (the same environment during the development of a.dll)

1.       Place the b.dll and testcsp.exe to c:\windows\system32

2.       Run command : regsvr32    b.dll  à result FAIL

3.       Run command : cspSign c   b.dll à result PASS

4.       Run command : regsvr32   b.dll à result FAIL

5.       Run testcsp.exe   à result PASS

 Question : Why both of the b.dll is PASS?

 

FYI, a.dll was compiled using Visual 6.0 and b.dll was compiled using Visual Studio 2005. Is the compiler cause the different result of during the testing?

 

Thank You.

CannotResolveSymbol
CannotResolveSymbol
{insert caption here}
Since you apparently still have not read the documentation that ZippyV linked earlier:

You do not replace advapi32.dll with your own library when you write a custom CSP.  You do not register your CSP using regsvr32.  Read the step-by-step guide to developing and testing a CSP, then come back and ask questions.
page 1 of 1
Comments: 1 | Views: 1619
Microsoft Communities