Unable to debug System.Net.DigestClient throws an exception

Question

I converted a VS2003 application to a VS2005 application. I have no errors and no warnings when I compile. When I attempt to run I get the error:

 

Unable to start debugging on the web server. The type initializer for 'System.Net.DigestClinet' threw an exception.

Any thoughts on how to fix this?

Answer 1

I am assuming this is an IIS web application. Is this correct?

Do you have the same problem for all web applications?

Do you have the same problem on all computers?

Answer 2

Yes this is an IIS web application.

I have hte same problem for any web application I try to convert. I do not get the error if I start a new project from scratch.

I have not tried it on any other computers as I am the first developper to attempt to do this at my company.

Answer 3

When you started from scatch, did you also make an IIS-based application?

Answer 4

Yes I also made an IIS based application starting from scratch. I made a watered down version of what my converted application does.

Answer 5

i have the same problem with,and even worth i can't debug any iis web applications include create a new one,SOS!

Answer 6

I am having the same problem.  Did you ever get a solution to this issue?  This is happening with both new and converted applications.

 

 

Answer 7

Nope still haven't gotten a resolution for this.

Answer 8

Anyone get this resolved?  I have the exact same problem.  There is very little in Google on this.  I can't even find System.Net.DigestClient in the framework.

 

Thanks,

Charles

Answer 9

Me too.. cannot debug from the IDE... I can of course attach to the asp.net process and do it that way, but it is a pain to have to do this each time I want to try something out.

I tried setting the security loads of different ways but no luck. Nothing in the Event log. No details ANYWHERE!

Absolutely no help anywhere!

How do you register a bug at Microsoft?

Answer 10

To open a bug: http://lab.msdn.microsoft.com/ProductFeedback/

We would be interested in knowing your operating system version, and anything about your IIS configuration that you think might be helpful in reproducing the problem.

Thanks!

Answer 11

maybe something wrong with the config things between framework1 and frame work 2.0,this happend both on server 2003 & xp pro, but i just meet this trouble with projects convert from vs2003,now i find a stupid way to avoid this problem:

open you vs2005  then set up a new iis site project,then run it ,every thing is ok, after this,close the current project (just close the current project not the vs2005) and open your trouble project in the same ide window ,everything should be allright now. not a smart way but it works. maybe vs2005 ide just wanna start from a framework 2.0 project ..hehe,BTW VS2005 still is a nice product ,i love ms ^_^.

Answer 12

 

Have any of you got a referenced assembly called Security.dll?

I read somewhere that if you have a dll of this name in your web bin folder, this will be used first for any basic security, and, of course, you will not have the relevant methods available.

I got this working by renaming the output of my Security.dll to have a fully qualified assembly name, so as to differentiate it from yer actual security.dll.

Answer 13

Thanks dork, u got the point

Answer 14

There hasn't been any activity on this thread for awhile, but there is good content here so I'm going to close this thread by marking it as answered.  If they thread originator would like to revive the thread, they can unmark it as answered.  Thanks.  -Noah Coad, VS Debugger PM

Answer 15

Did it ever occur to you that there's been no activity because YOU haven't answered the question??

Your signature line indicates that you are the VisualStudio Debugger Project Manager, if that's true why don't YOU provide US an answer!!??!!

Answer 16

was having similiar situation with same error message.  try removing references and readding them, and restart solution/project...

Answer 17

Thanks, dork

I was experiencing the same issue - i had a DLL called Security.dll. 

After renaming it, the problem's gone :)

Answer 18

You guys are right - there is precious little on this out on Google.  I ran into the same problem and tried fully qualifying the assembly name of my custom Security.dll assembly, as suggested above, but it didn't help.  In the end I just bit the bullet and renamed it lock, stock and barrel and the problem went away.

Answer 19

I got this exact error and your solution works! :) Thank you for posting this...

Answer 20

Nice Dork,

 

That was my problem, I created a new security project last week, forgot to fully qualify the assembly name when I created it, got pulled off on something else, and a week later after i cranked up VS with this solution, i had the problem.

 

Fully qualfying the Security.dll to CompanyName.Security.dll solved the issue.