Archives
-
Mentoring Service for New Code Camp Presenters
One of the things that was discussed between Stan and some of the presenters at the Philly Code Camp was the task of getting more people from the local community, and focusing less on “well known” speakers. Someone (and I can’t remember who) suggested that the problem with getting people new to presenting to volunteer is the lack of some sort of a mentoring program. The idea is to get people who are out in the field every day and help them present some of the new/interesting things that they are doing with .Net. Local user groups are a good way to start (that is how I started), but Code Camps are also attracting folks that don’t normally attend user groups. To help them get over any fear/uncertainty, it was suggested that the Code Camps offer a mentoring service to people that haven’t presented before. Now, I’m not Scott Hansleman or Don Box, but I have done a few presentations (and I’m definitely not bashful about speaking in public, it’s getting me to shut up that can be the problem), so if anyone feels like presenting at a Code Camp, and would like someone to bounce questions off of, I’m offering my services. If you don’t already have my email address, just use my contact page.
-
NUnit Testing and Application.LocalUserAppDataPath Property
Here’s a note to myself (and for anyone else that is doing Test Driven Development). If you are using the Application.LocalUserAppDataPath property, when running tests, the properties value will not be the same as if you are running in the application. That’s because LocalUserAppDataPath is built the following way: Base Path\ CompanyName\ ProductName\ ProductVersion, and the CompanyName, ProductName, and ProductVersion are all derived from the AppDomain. The AppDomain gets this info from the AssemblyInfo attributes of the exe, not the dll. Since I was testing a dll, the tests failed, since the exe that created the AppDomain was generated by my testing tool (TestDriven.Net), which did not have any of the AssemblyInfo attributes set. The result was that the Application.LocalUserAppDataPath was User\1.0.0.0. I’ve got to send a request to Jamie, and see if we can update the ProcessInvocation.exe to reflect the AssemblyInfo in the dll that is being tested.
The preceding blog entry has been syndicated from the DonXML Demsak’s All Things Techie Blog. Please post all comments on the original post.