Getting Familiar with the My Namespace - 24
- Posted: Nov 21, 2011 at 9:30 AM
- 16,623 Views
- 6 Comments
This video demonstrates the use of the My Namespace in Visual Basic which provides a short-cut to often used classes in the .NET Framework Class Library. We demonstrate how to use the My Namespace to retrieve information about the user's computer, search for files on the file system, perform file and directory manipulation, get command line arguments, work with application settings and more.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More posts in this series
-
Understanding Event Driven Programming - 23
-
Getting Familiar with the My Namespace - 24
-
Concluding Thoughts - 25
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
I use the My namespace all the time. It is a great thing to remember newbies!
Thanks Bob for the command line Arguments and the
I never knew about that!
Bob,
Thankyou very much for your clear, percise informative lessons !!!
Don in Florida
@Don Friedman: Thanks Don! Glad they were helpful.
Hello. First of all thanks for a great series. One question what happens at 12:31? The names shown in the console window show Brian and Chuck but the names assigned to the settings were Bob and Steve (11:44). Brian and Chuck were assigned later approx. 13:30...
@Kari Holgarsson: Great catch. I think you caught me here pulling a slight-of-hand ... I actually ran through this exercise off camera once (a practice run). I think the values were cached somehow -- perhaps those values were cached in the output directory (/bin) somehow. I **forgot** about this otherwise I would have probably re-recorded it. If you write the code yourself during this exercise, you will get the correct results. Sorry for the confusion.
Ok, thanks for the explanation ;-) I will try the exercise myself, I was just wondering if some values could be "stock" in memory (unable to update) as this could be very difficult to debug in a more complex code.
Remove this comment
Remove this thread
close