"Ever need to test emails from an application, but don't necessarily want it sending them out? Don't want to hassle with pointing it to a physical SMTP server? All you want to is verify it can send email, and take a look at the message.

Papercut is your answer. Papercut is a simplified SMTP server designed to only receive messages (not to send them on) with a GUI on top of it allowing you to see the messages it receives. It doesn't enforce any restrictions on addresses, it just takes the message and allows you see it. It is only active while it is running, and if you want it in the background, just minimize it to the system tray. When it receives a new message, a balloon message will show up to let you know."

 

Download here

Blog post: Testing Emails in a Dev Environment

 

Enjoy!

Tags: .net. microsoft, .NET, ASP.NET, C#, _list

Seems I'm winning another Lotto card today :) ().

 

Joe posted for an online training material for ASP.NET MVC. Interested? Check them out:

Free ASP.NET MVC Training Online

 

Happy MVCing ;)

Tags: MVC, ASP.NET, .NET, C#, Joe Stagnar, ms-joe

"Convert Between VB, C#, C++, & Java with the most Accurate & reliable source code converters"

 

Check out more here: Tangible Software Converters

 

Hope it helps,
Regards

Tags: C#, soure code converters, Tangible Software Converters, VB

As part of a Silverlight applicatin I am currently developing, I have a small API that ships with the application that allows extending it with more features. I had few "Default" implementations inside the API and hence I placed them within a Namespace where all classes are marked as Internal.

Now, when I started working on the app, I created a Visual Studio Blank Solution. So the Silverlight application and the API are in the same blank empty solution inside VS 2008. When I access the main Namespace of the API, I always get to see the name of the default implementations, however as empty since all classes inside it are internal. 

So how can I hide the Namespace that contains all those implementations? I read this blog here "http://www.bartlannoeye.be/blog/2008/08/06/MakeCNamespaceInternal.aspx" which helped me do what I want, but I thought of illustrating a bit more here in this post to clarify the idea more.

Rule 1: Make sure all the classes inside the Namespace you want to hide are marked as Internal.

Rule 2: If you add a reference to a project whose source code is in the same solution, you will always see the Namespace name however empty with no classes.

Rule 3: If you add a reference to a project whose source code is not present in the current application, the Namespace name that contains all internal classes will be hidden.

 

I tried it out and seems to work very nice.

Hope this helps,
Regards

Tags: C#, silverlight 2.0

Here is an interesting review on my book by Travis Illig that I was referred to by Jim Minatel

Book Review: Professional ASP.NET 3.5 Security, Membership, and Role Management with C# and VB

Here is an excerpt of Travis review:

"Chapter 18, though, is where you'll want to flip right to. This is where it all comes together - all the stuff you'll have learned from the previous chapters, put together in a near-checklist form, so you can take a step back from the application you're working on, look through this, and ask yourself, "Am I doing this in a secure fashion?" Common gotchas and attacks are discussed here as well as ways to protect yourself.

It's definitely not for folks new to ASP.NET - if you haven't written an ASP.NET app before or you're just starting out, this isn't for you. This book gives you in-depth information that, in some cases, you'd only otherwise get by using .NET Reflector to delve into the actual .NET assemblies and follow the code. It's heavy, detailed information. For mid-level to experienced ASP.NET developers, you definitely need to pick this up.

In all, this is one of those books I'm really glad to have on my shelf, right alongside Professional ASP.NET 3.5 in C# and VB."

Hope you enjoy reading this review and reading the book :)

Regards

Tags: ASP.NET 3.5, ASP.NET 3.5 Sevurity, C#, Membership, Role Management, VB

I had a need to execute some Windows Keystrokes in an application we are developing inside Windows Explorer, it is a Shell Namespace Extension, a virtual drive for an in-house EDMS. The keystroke to execute was an "F5" key. In other words, after performing an operation, I wanted to programamtically hit F5.

I posted on one of the forums and they refered me to this article: SendKeys in C++. It happened that this article is also written by a Lebanese guy, Elie :)

So I read this article and tried to search for SendKeys in C# and found a link to the System.Windows.Forms.SendKeys class that you can reach here: SendKeys in C#. Not only this class can be used within Windows Applications, but also within applications developed against Windows operating system itself, mainly a Shell Namespace Extension.

The way to execute a keystroke is simply call the following:

SendKeys.Send("{F5}");

 

That's all what you need to do!

Regards

Tags: C#

Community Nights Session

Software Design Patterns

Rabeeh Abla (Software Architect - GlobalVision)

Monday, August 11, 2008 - 6:00 - 8:00 PM
Microsoft office

Please use the REGISTRATION PAGE to register for the session. Seats are limited, make sure you confirm your attendance once you receive the email upon regisration.

Note: If you have any problem with registration, please contact Bilal Haidar:

Tags: C#, lebdev.net

I passed by the following website that contains a tutorial of 22 Lessons on C#.

If you are newly learning C#, make sure to check it here (http://www.csharp-station.com/Tutorial.aspx) 

 

Hope this helps,
Regards

Tags: ASP.NET, C#