Where does codebehing run?

  • Thread starter Thread starter Ray Stevens
  • Start date Start date
R

Ray Stevens

I am attempting to test a VeriSign account and the setup instructions stated
that the certs file needed to go into the Windows\System32 folder. I am
getting an error from the code-behind assebly stating it cannot find it in
the certs chain and is pointing to a path in C:\Program Files\Microsoft
Visual Studio 8\Common 7\IDE.

Where should I put the certs folder?
 
Let's analyze the problem. Verisign provides you with instructins for
setting up a Verisign account on your machine. You're getting an error from
some ASPX page you wrote, saying that it can't find "the certs chain." The
Verisign instructions told you that you had to put "the certs file" in "the
Windows\System32 folder." And finally, you want to know where to put the
certs folder.

Now, once we clear away all the ASP.Net debris from your problem, we're left
with this:

1.Verisign provided you with insturctions for setting up a Verisign account
on your machine.
2. The instructions apparently told you where to put "the certs file."
3. You are asking us where to put "the certs folder."

The answer is, therefore, put the certs folder where Verisign told you to
put it.

And fix your code bug.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
 
Thank you for the unnecessarily insulting response. I hope it wasn't too
much trouble.

And, FYI, I DID put them where they told me but that didn't work when
running the IDE debugger. However, I did find that putting a copy of the
certs folder in COMMON rather than Windows\System32 (as the VeriSign readme
instructed) solved the problem in my development environment.
 
Unecessarily insulting. Would you please point out to me where I insulted
you? I analyzed your problem. Sorry if I wasn't touchy-feely enough for you.
I suppose that comes from interacting almost exclusively with computers
every day, instead of people. I have a tendancy to strip out all the
non-essentials from my communications.

But I'll ignore your characterization. Let's have another look at the issue:
And, FYI, I DID put them where they told me but that didn't work when
running the IDE debugger. However, I did find that putting a copy of the
certs folder in COMMON rather than Windows\System32 (as the VeriSign
readme
instructed) solved the problem in my development environment.
Click to expand...

Okay, the Verisign instructions told you to put the folder somewhere. Your
code didn't work with the folder where Verisign told you to put it. Instead
of changing your code, which I recommended, you changed the location of the
folder. Now it seems to work.

Of course, neither you nor I have any idea WHY Versign told you to put the
folder there. There may have been a reason for putting it in that specific
location. There may not have been. I suppose you'll find out eventually.
However, in the meantime, I would still stick with my advice. Why? Because
manufacturers recommendations are usually correct.

You had 2 choices: Move the folder, or fix your code. You chose the former,
and I recommended the latter. You will have to live with your choice. I
honestly hope it works out for you.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
 
Kevin Spencer said:
Okay, the Verisign instructions told you to put the folder somewhere. Your
code didn't work with the folder where Verisign told you to put it. Instead
of changing your code, which I recommended, you changed the location of the
folder. Now it seems to work.
Click to expand...

Although VeriSign supports dotnet, their sample and readme was sparse and
not particualy useful. They provided a basic sample aspx page and a readme
file, which worked... but nothing for the IDE, which didn't.

I'm not a web programmer, so how to fix the code was not obvious...
especially since the VeriSign dll does not come with source.

The path appears to be environment specific. (For example, on the dev
depolyment server I had to put it in windows\system32\inetsrv\certs).
 
Thank you for the unnecessarily insulting response. I hope it wasn't too
much trouble.
Click to expand...

LOL - I'd just put Kevin on my kill list thinking it was just me that caused
him to respond in such a insulting manner. Glad I'm not alone. I've been
using Usenet for many years now and I've only blocked a handful of people in
that time.

Rob.
 
Unecessarily insulting. Would you please point out to me where I insulted
you? I analyzed your problem. Sorry if I wasn't touchy-feely enough for
you.
Click to expand...

Kevin - that might be the problem, you don't know you are doing it...

Rob.
 
An insult is deliberate. You can't insult someone without knowing it. Some
people are thin-skinned, paranoid, or what-have-you, and take plain and
simple language as insulting. Is that the fault of the speaker?

Again, point out to me where I insulted Ray. I analyzed his problem. I broke
it down into manageable pieces, eliminated the fluff, and gave him his
options. That's what I get paid for every day as a programmer.

If you want touchy-feely, go to AOL.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
hey guys we should always respect each others. without any problems. we are
here to search for help and to help each others.
so let us talk about asp.net and how can we solve the problems we face in
our applications without caring about anyother thing.
thank you
wish you respect my point of view.
 
wish you respect my point of view.

I do!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
It may not have been deliberate, but you do come across with an unusually
condescending tone that is not typical in these newsgroups... and your
entire post could have been more efficiently distilled down to one sentence:
"Fix your code bug."

Now, just how useful is that advice? Especially when the VeriSign dll
accessing the certs doesn't come with source code and the samples and readme
were sparse, at best.
 
Back
Top