When the offending line throws, paste the exception and the stack. Before you copy the stack, right click on the Call Stack window and choose Show External Code (or something like that)).
From: [email protected] [mailto:[email protected]] On Behalf Of Ian Thomas Sent: Wednesday, October 12, 2011 9:13 PM To: 'ozDotNet' Subject: RE: first chance exception David This is with a breakpoint set a few lines below the "offending" line, but seems the same if it's at the same line - > XSDTest2.exe!XSDTest2.XSDTest.Program2.Main(String() args = > {Length=0}) Line 64 Basic [Native to Managed Transition] [Managed to Native Transition] Microsoft.VisualStudio.HostingProcess.Utilities.dll!Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() + 0x47 bytes mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x9b bytes mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x4d bytes Now, with fuslogvw running under admin privileges, running the small app under Debug or from its Release command prompt (it's a tiny command line thing), there's nothing to report in the log, after refresh (I left the default logging location, which I assume it can find and report, if it's not empty; and 'Log all binds to disk' was selected). I see that I have 2 versions of the logger - v3.5 and v4.0 (64-bit) - provided with VS and the Windows SDK - but both can run enabled, and neither reports anything after running my app. None of this is illuminating me yet (but I appreciate the help / education from all of you) ________________________________ Ian Thomas Victoria Park, Western Australia ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of David Kean Sent: Thursday, October 13, 2011 11:45 AM To: ozDotNet Subject: RE: first chance exception Can you paste the call stack when the first chance exception occurs? From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Joseph Clark Sent: Wednesday, October 12, 2011 8:03 PM To: ozDotNet Subject: Re: first chance exception Try using the Assembly Binding log viewer (fuslogvw<http://msdn.microsoft.com/en-us/library/e74a18c4%28v=vs.71%29.aspx>) to see where it is binding the serializer assemblies from (make sure it is configured to log all binds to disk). On Thu, Oct 13, 2011 at 1:54 PM, Ian Thomas <[email protected]<mailto:[email protected]>> wrote: Looked everywhere under my user account, for all DLLs. But even w/o locating it/them, should Debug show the first chance exceptions after I have done the generation? I would have thought the message would disappear. ________________________________ Ian Thomas Victoria Park, Western Australia ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David Kean Sent: Thursday, October 13, 2011 8:46 AM To: ozDotNet Subject: RE: first chance exception Where are you looking? I believe they generate them in the temp directories somewhere. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ian Thomas Sent: Wednesday, October 12, 2011 5:18 PM To: 'ozDotNet' Subject: first chance exception As I understand the documentation, Generate Serialization Assembly should produce a DLL ("Serialization assemblies are named TypeName.XmlSerializers.dll"). Is that right? I don't see any DLLs, and I still receive the The FileNotFoundException (which are first-chance handled exceptions) in debug. I did explicitly set it On. I know (from David Kean's advice) these FileNotFoundExceptions are nothing to worry about, but I'd like to see reality match MSDN documentation. ________________________________ Ian Thomas Victoria Park, Western Australia ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David Kean Sent: Wednesday, October 12, 2011 2:12 PM To: ozDotNet Subject: RE: XMLSerializer error The FileNotFoundException (which are first-chance handled exceptions and not unhandled) are expected - the XmlSerializer looks for a pre-compiled serialization assembly before it generates one on the fly. You can pre-generate serialization assemblies via the Generate serialization assembly option on the Build tab of the Project properties.
