I'm curious as to the number of applications being produced for the .NET
framework.  This may not be the best place to ask the question because the
response may be slightly biased.  But, it seems to me that much of the hype
has gone by the wayside.  Personally, I could care less about developing for
..NET.  Please let me know if I'm out of touch and need to get on the .NET
wagon or my livelyhood will go down the tubes.  Win64 API anyone?

As for Office 2007, is it native or .NET?  Does anyone know?

Thanks,
B Miller

I have been using .NET and C# with Microsoft Visual Studio 2005 for some time now and really like it.

My development time is easily cut in half and less prone to bugs.

Linking to Office 2007 is done directly with .NET libraries.

For Example to send an email via Outlook you just use something like the following code:


Outlook.Application OA = new Outlook.Application();
Outlook.MailItem eMail = (Outlook.MailItem)OA.CreateItem(Outlook.OlItemType.olMailItem);

eMail.Subject = "Test eMail";
eMail.To = "mail@somebody.com";
eMail.Body = "This is a test eMail";

eMail.Send();

Chris Holland
SEC Solutions Ltd.

B Miller wrote:
> I'm curious as to the number of applications being produced for the .NET
> framework.  This may not be the best place to ask the question because the
> response may be slightly biased.  But, it seems to me that much of the hype
> has gone by the wayside.  Personally, I could care less about developing for
> .NET.  Please let me know if I'm out of touch and need to get on the .NET
> wagon or my livelyhood will go down the tubes.  Win64 API anyone?
>
> As for Office 2007, is it native or .NET?  Does anyone know?
>
> Thanks,
> B Miller
>
>

Thanks Chris.  My question about Office 2007 is if MS wrote it as a .NET
application.  Are they adhering to the rules that they want everyone else to
follow?  Or are they skipping .NET for their own apps?

The marketplace demands compatibility with various versions of windows.  I
haven't seen where the marketplace has demanded .NET.  I don't think the
average user knows or cares as long as their program works and doesn't
consume a huge amount of resources.

B Miller

"Chris Holland" <mail@chrisholland.me.uk> wrote in message
news:7ACC7B7C-5B99-4ADF-AEFB-E5F4374DCAF0@news.elevatesoft.com...
>I have been using .NET and C# with Microsoft Visual Studio 2005 for some
>time now and really like it.
>
> My development time is easily cut in half and less prone to bugs.
>
> Linking to Office 2007 is done directly with .NET libraries.
>
> For Example to send an email via Outlook you just use something like the
> following code:
>
>
> Outlook.Application OA = new Outlook.Application();
> Outlook.MailItem eMail =
> (Outlook.MailItem)OA.CreateItem(Outlook.OlItemType.olMailItem);
>
> eMail.Subject = "Test eMail";
> eMail.To = "mail@somebody.com";
> eMail.Body = "This is a test eMail";
>
> eMail.Send();
>
> Chris Holland
> SEC Solutions Ltd.
>
> B Miller wrote:
>> I'm curious as to the number of applications being produced for the .NET
>> framework.  This may not be the best place to ask the question because
>> the response may be slightly biased.  But, it seems to me that much of
>> the hype has gone by the wayside.  Personally, I could care less about
>> developing for .NET.  Please let me know if I'm out of touch and need to
>> get on the .NET wagon or my livelyhood will go down the tubes.  Win64 API
>> anyone?
>>
>> As for Office 2007, is it native or .NET?  Does anyone know?
>>
>> Thanks,
>> B Miller

"B Miller" <bmiller@nospam.com> wrote in message
news:7B2DECEF-3C71-4AC7-A675-8BA30AF239F5@news.elevatesoft.com...

> My question about Office 2007 is if MS wrote it as a .NET application.

Office is still a win32 application. Smaller parts may be .NET.