Vista - Migrating a .Net1.1 Email Notification Service to .Net 3.5

06-27-2008

Thanks for the advice, Jeroen!!

"Jeroen Mostert" wrote:

Quote:

> xyz_jat wrote:

Quote:

> > I'm planning to re-engineer an Email Notification Service (Windows Service)
> > in C# using .net framework 3.5 which was previously written in c# using .net
> > framework 1.1. In the old version, Lotus Notes and Domino were used to
> > process the notifications and in newer version we are planning to use SMTP
> > instead of Domino.
> >

> Be aware that .NET has no support for *incoming* mail protocols as part of
> the framework. As long as you only need to *send* mail, SMTP will do fine.
>
> As far as the transition from 1.1 to 3.5 goes, your main hurdle is going
> from 1.1 to 2.0. The 3.5 framework is just the 2.0 SP1 runtime with
> additional classes, so the change from 2.0 to 3.5 isn't nearly as substantial.
>
> Even so, most code "just works" when you recompile it, though you may get
> deprecation warnings about constructs no longer supported in 1.1. Rewriting
> these is usually fairly easy. Here's a detailed post on the migration, which
> works more or less the same for going straight to 3.5 and VS 2008:
> http://blogs.msdn.com/peterlau/archi...11/595294.aspx
>
> --
> J.
>

06-27-2008

xyz_jat wrote:

Quote:

> I'm planning to re-engineer an Email Notification Service (Windows Service)
> in C# using .net framework 3.5 which was previously written in c# using .net
> framework 1.1. In the old version, Lotus Notes and Domino were used to
> process the notifications and in newer version we are planning to use SMTP
> instead of Domino.
>

Be aware that .NET has no support for *incoming* mail protocols as part of
the framework. As long as you only need to *send* mail, SMTP will do fine.

As far as the transition from 1.1 to 3.5 goes, your main hurdle is going
from 1.1 to 2.0. The 3.5 framework is just the 2.0 SP1 runtime with
additional classes, so the change from 2.0 to 3.5 isn't nearly as substantial.

Even so, most code "just works" when you recompile it, though you may get
deprecation warnings about constructs no longer supported in 1.1. Rewriting
these is usually fairly easy. Here's a detailed post on the migration, which
works more or less the same for going straight to 3.5 and VS 2008:
http://blogs.msdn.com/peterlau/archi...11/595294.aspx

--
J.

07-23-2008

Thanks for the advice, Jeroen!!

"Jeroen Mostert" wrote:

Quote:

> xyz_jat wrote:

Quote:

> > I'm planning to re-engineer an Email Notification Service (Windows Service)
> > in C# using .net framework 3.5 which was previously written in c# using .net
> > framework 1.1. In the old version, Lotus Notes and Domino were used to
> > process the notifications and in newer version we are planning to use SMTP
> > instead of Domino.
> >

> Be aware that .NET has no support for *incoming* mail protocols as part of
> the framework. As long as you only need to *send* mail, SMTP will do fine.
>
> As far as the transition from 1.1 to 3.5 goes, your main hurdle is going
> from 1.1 to 2.0. The 3.5 framework is just the 2.0 SP1 runtime with
> additional classes, so the change from 2.0 to 3.5 isn't nearly as substantial.
>
> Even so, most code "just works" when you recompile it, though you may get
> deprecation warnings about constructs no longer supported in 1.1. Rewriting
> these is usually fairly easy. Here's a detailed post on the migration, which
> works more or less the same for going straight to 3.5 and VS 2008:
> http://blogs.msdn.com/peterlau/archi...11/595294.aspx
>
> --
> J.
>

06-27-2008	#1 (permalink)
xyz_jat n/a posts	Migrating a .Net1.1 Email Notification Service to .Net 3.5 Thanks for the advice, Jeroen!! "Jeroen Mostert" wrote: Quote: > xyz_jat wrote: Quote: > > I'm planning to re-engineer an Email Notification Service (Windows Service) > > in C# using .net framework 3.5 which was previously written in c# using .net > > framework 1.1. In the old version, Lotus Notes and Domino were used to > > process the notifications and in newer version we are planning to use SMTP > > instead of Domino. > > > Be aware that .NET has no support for incoming mail protocols as part of > the framework. As long as you only need to send mail, SMTP will do fine. > > As far as the transition from 1.1 to 3.5 goes, your main hurdle is going > from 1.1 to 2.0. The 3.5 framework is just the 2.0 SP1 runtime with > additional classes, so the change from 2.0 to 3.5 isn't nearly as substantial. > > Even so, most code "just works" when you recompile it, though you may get > deprecation warnings about constructs no longer supported in 1.1. Rewriting > these is usually fairly easy. Here's a detailed post on the migration, which > works more or less the same for going straight to 3.5 and VS 2008: > http://blogs.msdn.com/peterlau/archi...11/595294.aspx > > -- > J. >
My System Specs

06-27-2008	#2 (permalink)
Jeroen Mostert n/a posts	Re: Migrating a .Net1.1 Email Notification Service to .Net 3.5 xyz_jat wrote: Quote: > I'm planning to re-engineer an Email Notification Service (Windows Service) > in C# using .net framework 3.5 which was previously written in c# using .net > framework 1.1. In the old version, Lotus Notes and Domino were used to > process the notifications and in newer version we are planning to use SMTP > instead of Domino. > Be aware that .NET has no support for incoming mail protocols as part of the framework. As long as you only need to send mail, SMTP will do fine. As far as the transition from 1.1 to 3.5 goes, your main hurdle is going from 1.1 to 2.0. The 3.5 framework is just the 2.0 SP1 runtime with additional classes, so the change from 2.0 to 3.5 isn't nearly as substantial. Even so, most code "just works" when you recompile it, though you may get deprecation warnings about constructs no longer supported in 1.1. Rewriting these is usually fairly easy. Here's a detailed post on the migration, which works more or less the same for going straight to 3.5 and VS 2008: http://blogs.msdn.com/peterlau/archi...11/595294.aspx -- J.
My System Specs

07-23-2008	#3 (permalink)
xyz_jat n/a posts	Re: Migrating a .Net1.1 Email Notification Service to .Net 3.5 Thanks for the advice, Jeroen!! "Jeroen Mostert" wrote: Quote: > xyz_jat wrote: Quote: > > I'm planning to re-engineer an Email Notification Service (Windows Service) > > in C# using .net framework 3.5 which was previously written in c# using .net > > framework 1.1. In the old version, Lotus Notes and Domino were used to > > process the notifications and in newer version we are planning to use SMTP > > instead of Domino. > > > Be aware that .NET has no support for incoming mail protocols as part of > the framework. As long as you only need to send mail, SMTP will do fine. > > As far as the transition from 1.1 to 3.5 goes, your main hurdle is going > from 1.1 to 2.0. The 3.5 framework is just the 2.0 SP1 runtime with > additional classes, so the change from 2.0 to 3.5 isn't nearly as substantial. > > Even so, most code "just works" when you recompile it, though you may get > deprecation warnings about constructs no longer supported in 1.1. Rewriting > these is usually fairly easy. Here's a detailed post on the migration, which > works more or less the same for going straight to 3.5 and VS 2008: > http://blogs.msdn.com/peterlau/archi...11/595294.aspx > > -- > J. >
My System Specs

Similar Threads
Thread	Forum
The system event notification service service failed logon ... token does not exist	General Discussion
system event notification service?????	Vista account administration
Systems Event Notification Service	Vista General
Email setup, migrating from word 2000 world	Vista installation & setup
System Event Notification Service service	Vista General