Cor you are so right, I'm not experienced enough and that's why
I ask these stupid questions that I don't understand or explain very well
and therefore I greatly appreciate your patience and input. I've had the
most stressful year of my life trying to maintain a salaried programming job
without enough experience and ability at debugging and I'm working on trying
to clarify my questions and problem solving.
Anyway, you are right the problem was due to the designer. I had set a
property
in a checkboxlist a .checkonitem boolean and for some reason VS seemed to
create and write in a file app.config an xml style entry that said
..checkonitem was set to false.
Anyway, this app.config setting was causing the code to hang when it got to
the codebehind syntax saying the same thing, that property is set to false.
So, anyway because I wasn't debugging this in VS and assumed by exporting the
debugger in my code I could get an accurate answer to what was
going on, I wasted time thinking it might be a larger problem because my
deployment at least had been working before. My manager reminded me to look
for the small problems first instead of assuming it's something else like a
..net 2.0 conflict or corrupted .net installation.
My sincere apologies.
I also had some troubles getting comfortable with setting up a shortcut in
the programs menu. The process to get it working just seemed
counterintuitive because you were dealing with some different filenames with
different properties.
Segue
"Cor Ligthert [MVP]" wrote:
Segue,
I don't know how expirienced you are, however mostly this kind of exceptions
start if you have changed things in the designer generated part.
Do you get this with a complete empty project as well?
Cor
"segue" <se***@discussions.microsoft.com> schreef in bericht
news:EC**********************************@microsof t.com...
Application has generated an exception that can't be handled.
I can't fix this after reinstalling .net which was the only solution
I could find on the net.
Suggestions appreciated.
Segue
