Upgraded to 4.2(RTM) and appropriate firmware on my N+.
Everything went fine, but now in my debug sessions I'm missing the RAM/ROM/META messages, which I really liked since I'm doing a lot of reflection, and it's nice to know how big the assemblies are that I'm loading.
Do I need to do anything differently now that I'm on the 4.2 SDK?
Debug info output?
Started by H07R0D, Feb 03 2012 08:58 PM
1 reply to this topic
#2
Novice Alex
-
- Members
-
- 59 posts
Advanced Member
Posted 04 August 2012 - 03:34 PM
Upgraded to 4.2(RTM) and appropriate firmware on my N+.
Everything went fine, but now in my debug sessions I'm missing the RAM/ROM/META messages, which I really liked since I'm doing a lot of reflection, and it's nice to know how big the assemblies are that I'm loading.
Do I need to do anything differently now that I'm on the 4.2 SDK?
Hi H07R0D,
I too looking at using reflection to set the debug statement printout during exception being thrown out. Can you share with me how to use the reflection methods to extract the name of the method (within the class) that is causing the exception?
In VB.NET, I always include these statements in my catch statement.
Dim f As New StackFrame cErrorHandler.LogError(f.GetMethod().DeclaringType.FullName & "." & System.Reflection.MethodBase.GetCurrentMethod().Name, ex)
Wonder how can I do the same in .NetMF 4.2
Thanks in advance.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
