.NET 3.0

  • Thread starter Thread starter Bill McCormick
  • Start date Start date
B

Bill McCormick

Hello C# programmers:

I'm began developing a client/server application in C#2.0. Do I gain
much by moving to 3.0?

One of the features that I'm just now getting my arms around is
Remoteing. Should I skip this and go right to the WCF?

Thanks,

Bill
 
Bill McCormick said:
Hello C# programmers:

I'm began developing a client/server application in C#2.0. Do I gain much
by moving to 3.0?
Click to expand...

I am not sure I can answer this without knowing more.

In 3.5 (or 3.0), you can use WPF for your UI instead of standard forms. With
the state of tools, this will mean purchasing Expression Blend and there are
still some things that are hard to do. You also get LINQ for manipulating
data objects. And you get WCF, which you ask about below.
One of the features that I'm just now getting my arms around is Remoteing.
Should I skip this and go right to the WCF?
Click to expand...

I would. Remoting is a pain in the butt to work with compared to WCF and you
end up completely rewriting bits if you have to make it openly accessible
via WSDL. With WCF, you just set up a new web endpoint and roll with it. So
there are two reasons:

1. Easier to set up (mostly declarative)
2. Ability to create standards based endpoints without rewriting

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************
 
Gregory said:
I am not sure I can answer this without knowing more.

In 3.5 (or 3.0), you can use WPF for your UI instead of standard forms. With
the state of tools, this will mean purchasing Expression Blend and there are
still some things that are hard to do. You also get LINQ for manipulating
data objects. And you get WCF, which you ask about below.


I would. Remoting is a pain in the butt to work with compared to WCF and you
end up completely rewriting bits if you have to make it openly accessible
via WSDL. With WCF, you just set up a new web endpoint and roll with it. So
there are two reasons:

1. Easier to set up (mostly declarative)
2. Ability to create standards based endpoints without rewriting
Click to expand...

OK, thanks. Also, do I need VS 2008 or greater to move into 3.0
territory? I want to come up to speed on all this new tech more quickly
and would consider a class or workshop. How would I go about finding a
decent one in my area (San Antonio)?
 
//Remoteing. Should I skip this and go right to the WCF?//


YES.

Let me say it again. YES.


Here is a simple but effective demo.


http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry


The WCF model is more effective way to code vs Remoting. WCF is more
"abstract", and allows you to write your code in one way...but provide
different endpoints (or ways to fish out your code). Aka, the same code can
serve up WebServices as it can Remoting.
Pre WCF, you had to code against 2 very different models.

.....................

You only go to 3.0 if you want the extra features. WCF and WWF (or WF)
(Windows Workflow Foundation)? They are "add-ons" to 2.0, not replacements.
http://www.google.com/search?hl=en&q=Windows+Workflow+Foundation
 
Gregory A. Beamer (Cowboy) - MVP wrote:








OK, thanks. Also, do I need VS 2008 or greater to move into 3.0
territory? I want to come up to speed on all this new tech more quickly
and would consider a class or workshop. How would I go about finding a
decent one in my area (San Antonio)?
Click to expand...

If you just want to move to .Net 3.0, you only need VS2005 with the
appropriate .Net 3.0 bits. You need VS2008 if you wish to use C# 3.0
with features like LINQ.

Chris
 
sloan said:
//Remoteing. Should I skip this and go right to the WCF?//


YES.

Let me say it again. YES.


Here is a simple but effective demo.


http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry


The WCF model is more effective way to code vs Remoting. WCF is more
"abstract", and allows you to write your code in one way...but provide
different endpoints (or ways to fish out your code). Aka, the same code can
serve up WebServices as it can Remoting.
Pre WCF, you had to code against 2 very different models.

....................

You only go to 3.0 if you want the extra features. WCF and WWF (or WF)
(Windows Workflow Foundation)? They are "add-ons" to 2.0, not replacements.
http://www.google.com/search?hl=en&q=Windows+Workflow+Foundation
Click to expand...
I see. I thought I needed to move to .NET 3.x to get WCF. So I can just
"add-on". Can you recommend some good reading to come to speed on WCF.

Thanks.
 
//original//
If you just want to move to .Net 3.0, you only need VS2005 with the
appropriate .Net 3.0 bits. You need VS2008 if you wish to use C# 3.0
with features like LINQ.
//adjusted//
If you just want to move to .Net 3.0, you only need VS2005 with the
appropriate .Net 3.0 bits. You need VS2008 if you wish to use C# 3.5
with features like LINQ.
Click to expand...


3.5 = LINQ
 
You need to get to (at least) level 3.0 to use WCF. However, 3.0 is just
additional libraries added to 2.0.
(as opposed to the 2.0 and 1.1 versions...2.0 was a STANDALONE REPLACEMENT
for 1.1).

Here are some links ... if you want to use VS2005/3.0



Microsoft .NET Framework Version 2.0 Redistributable Package (x86)
http://www.microsoft.com/downloads/...CB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

------------------------

Microsoft .NET Framework 3.0 Redistributable Package
http://www.microsoft.com/downloads/...0b-f857-4a14-83f5-25634c3bf043&DisplayLang=en

(Please note that 3.0 is add-on components to 2.0, and not a replacement for
2.0)


------------------------

Visual Studio 2005
(NOTE: Items which can be ~omitted~ in VS2005 install:
J#
C++
)

------------------------


Visual Studio 2005 Service Pack 1 (SP1)
http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx

------------------------

------------------------

Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November
2006 CTP
http://www.microsoft.com/downloads/...37-cc86-4bf5-ae44-f5a1e805680d&DisplayLang=en


------------------------

Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow
Foundation)
http://www.microsoft.com/downloads/...9E-1FA3-48CF-8023-E8F38E709BA6&displaylang=en


------------------------
 
Hi Bill,

If your application will need to adopt some districuted communication
components, on windows/.NET platform, WCF should be the preferred one.

For ram up, I think the get start section in MSDN is good which contains
some basic walkthroughss:

#Getting Started Tutorial
http://msdn.microsoft.com/en-us/library/ms734712.aspx

Also, you can inspect the WCF samples from windows sdk:

http://blogs.msdn.com/dotnetinterop/archive/2008/03/24/the-wcf-samples-have-
been-updated.aspx

In addition, you can always get many new articles on WCF official sites:

#Windows Communication Foundation home

http://netfx3.com/content/WCFHome.aspx

http://netfx3.com/content/WCFHome.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
 
Steven said:
Hi Bill,

If your application will need to adopt some districuted communication
components, on windows/.NET platform, WCF should be the preferred one.

For ram up, I think the get start section in MSDN is good which contains
some basic walkthroughss:

#Getting Started Tutorial
http://msdn.microsoft.com/en-us/library/ms734712.aspx

Also, you can inspect the WCF samples from windows sdk:

http://blogs.msdn.com/dotnetinterop/archive/2008/03/24/the-wcf-samples-have-
been-updated.aspx

In addition, you can always get many new articles on WCF official sites:

#Windows Communication Foundation home

http://netfx3.com/content/WCFHome.aspx

http://netfx3.com/content/WCFHome.aspx
Click to expand...

Thanks Steven. Would you please enlighten me on upgrading from VS 2005
to VS 2008? Is it recommended that 2005 be completely uninstalled first?

Thanks,

Bill
 
I apologize.

I meant of course, the Framework Versions.

VS2005= Framework 2.0/3.0.

VS2008 = Framework 3.5 (or backwards)

I meant for him to notice you can't do Framework 3.5 stuff with VS2005.

Sorry for incorrectly .. correcting you!
 
You may still find some tools for 3.0 in 2005, but


Bill McCormick said:
OK, thanks. Also, do I need VS 2008 or greater to move into 3.0 territory?
Click to expand...

I think you might find the 3.0 bits for VS2005, but I would go to VS2008
with SP1 and work with the latest (3.5 SP1). There is no reason to learn the
second latest when you can do the latest.
I want to come up to speed on all this new tech more quickly and would
consider a class or workshop. How would I go about finding a decent one in
my area (San Antonio)?
Click to expand...

If you want Microsoft training, you can try the Microsoft learning site.
There are plenty of online classes that might work (much cheaper):
http://learning.microsoft.com/manager/catalog.aspx

There is also a search engine:
http://www.microsoft.com/learning/classlocator/

But it is not showing San Antonio centers, so try New Horizons -- location:
8200 Ih 10 W # 500, San Antonio, TX 78230

Their site is:
http://www.newhorizons.com

The schedule for San Antonio is:
http://www.newhorizons.com/content/NH_FullSchedule.aspx?SiteID=91

It looks like there is a Visual Studio course, but not until March 2009.

One site you should become familiar with is www.netfx3.com. It is the site
for the new technologies in 3.x. There are plenty of videos, sample apps,
etc. Great way to learn. Also familiarize yourself with www.asp.net for the
latest in web technologies and www.silverlight.net for Silverlight (WPF for
the web) learning and samples.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************
 
No need to uninstall. They install side-by-side. For a time, I was using
both. As none of my 2.0 apps will not compile 2.0 in VS2008, the only VS2005
I still have is for SQL Server Management Studio. And it is only there
because the VS2008 version (for SQL 2008) sucks when connecting to a SQL
2005 Database server. Once we switch to SQL 2008, I will can VS2005
completely.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************
 
I apologize.

I meant of course, the Framework Versions.

VS2005= Framework 2.0/3.0.

VS2008 = Framework 3.5 (or backwards)

I meant for him to notice you can't do Framework 3.5 stuff with VS2005.

Sorry for incorrectly .. correcting you!
Click to expand...

I was pretty sure that's what you meant. MS has muddied up the waters
with the way they have done their version numbers.

Chris
 
Bill said:
I'm began developing a client/server application in C#2.0. Do I gain
much by moving to 3.0?

One of the features that I'm just now getting my arms around is
Remoteing. Should I skip this and go right to the WCF?
Click to expand...

If that client/server solution is expected to run for
many years, then going directly to WCF from the beginning
seems as a good strategic move.

Arne
 
Hi Bill,

Yes, as Gregory mentioned, vs 2008 can be installed with VS 2005 together
without any problem. Side by side is supported.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
 
Back
Top