Maintaining WS issues

[eschneider]

Just some common issues with WS:

Using custom objects: When objects change, seems you are always fixing some
issue. Update references, which sometimes does not work.

Deployment:
Weird errors which take a while to fix because the error stink:
Forget to set ASP.NET 2.0="Parser Error Message: Could not load
type"
'*.Global' is ambiguous: it could come from assembly=I deleted the
following folders "Bin", "App_Code".

Different OS versions: have different deployment requirements/Security on
the box. (Think It could be easier, It's a public internet exposed service,
or it's a corporate internal service)

Is the WS running? Where is it running? IIS or VS? what is the URL?
Where is the WS folder? Is it virtual?
They slow down VS solutions.
MS keeps changing how everything works together, all the time, making hard
to keep up with. (IIS vs. VS dev server, Security fixes)

Debugging is a pain, also seems you must step into them, to get it working.
Also make sure you have it running first.

There is a lot more: VSS, and others I can't think of now.

WS Just seem to be a pain to maintain...

We have reached the point that we no longer use them unless we need to
interact with other technologies.
We tend to use mostly remoting now.

WCF seems to be better, but still seem it will suffers some of this.

We are currently using VS2005 pro.

Does anyone else have these issues?

Thanks,
Schneider

[Steven Cheng [MSFT]]

RE: Maintaining WS issues

Hi eschneider,

Regarding on the issues you mentioned, some of them does exists when
dealing with some certain kind of projects in Visual Studio 2005. The
global classe issue maybe caused by a project converted from ASP.NET
1.1/VS 2003 project since the global class converted from original project
may confliect with a new one.

For the different deployment requirement, do you mean the IIS server? I
know that it may require different configuration for deploying web
application in IIS 5 and IIS 6 since they have different process model.
also, for the Visual Studio internal dev webserver, it is used for
developmente/test only, it can not be used for production(only accessible
from local machine).

I can understand your concerns that new features are kept being added into
Visual Studio and some functionality seems hard to use and may raise
problems. However, the visual tools and .net framework teams are really
working hard to address most of the issues. Actually most of the new
features also come from the community feedback and comments. Sure, there
may still occur problems in the new version of Visual Studio, but our dev
engineer will keep improving them. And those comments and feedback from
commuinty are really important and valuable for our improvement. You're
welcome to submit them to the connect site:

#Visual Studio and .NET Framework - English

https://connect.microsoft.com/feedback/default.aspx?SiteID=210&wa=wsignin1.0

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:
msdnmg@microsof t.com.

=============== =============== =============== =====
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif

ications.

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://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
Reply-To: "eschneider " <eschneider@com munity.nospam>
From: "eschneider " <eschneider@com munity.nospam>
Subject: Maintaining WS issues
Date: Thu, 17 Apr 2008 14:07:27 -0500

Just some common issues with WS:

Using custom objects: When objects change, seems you are always fixing some
issue. Update references, which sometimes does not work.

Deployment:
Weird errors which take a while to fix because the error stink:
Forget to set ASP.NET 2.0="Parser Error Message: Could not load
type"
'*.Global' is ambiguous: it could come from assembly=I deleted the
following folders "Bin", "App_Code".

Different OS versions: have different deployment requirements/Security on
the box. (Think It could be easier, It's a public internet exposed service,
or it's a corporate internal service)

Is the WS running? Where is it running? IIS or VS? what is the URL?
Where is the WS folder? Is it virtual?
They slow down VS solutions.
MS keeps changing how everything works together, all the time, making hard
to keep up with. (IIS vs. VS dev server, Security fixes)

Debugging is a pain, also seems you must step into them, to get it working.
Also make sure you have it running first.

There is a lot more: VSS, and others I can't think of now.

WS Just seem to be a pain to maintain...

We have reached the point that we no longer use them unless we need to
interact with other technologies.
We tend to use mostly remoting now.

WCF seems to be better, but still seem it will suffers some of this.

We are currently using VS2005 pro.

Does anyone else have these issues?

Thanks,
Schneider

[eschneider]

Re: Maintaining WS issues

Hello, Steven
Nice to hear back from MSFT.

It may be a lot better in VS2008 and/or with WCF. But we have not had a
chance to move to VS2008.
I have heard from people WCF is much better. The IIS version probably have
contributed to some of the problems, but then that part of the problems with
webservices.

Thanks,
Schneider


"Steven Cheng [MSFT]" <stcheng@online .microsoft.comw rote in message
news:8%23cHOfPo IHA.9016@TK2MSF TNGHUB02.phx.gb l...

Hi eschneider,
>
Regarding on the issues you mentioned, some of them does exists when
dealing with some certain kind of projects in Visual Studio 2005. The
global classe issue maybe caused by a project converted from ASP.NET
1.1/VS 2003 project since the global class converted from original project
may confliect with a new one.
>
For the different deployment requirement, do you mean the IIS server? I
know that it may require different configuration for deploying web
application in IIS 5 and IIS 6 since they have different process model.
also, for the Visual Studio internal dev webserver, it is used for
developmente/test only, it can not be used for production(only accessible
from local machine).
>
I can understand your concerns that new features are kept being added into
Visual Studio and some functionality seems hard to use and may raise
problems. However, the visual tools and .net framework teams are really
working hard to address most of the issues. Actually most of the new
features also come from the community feedback and comments. Sure, there
may still occur problems in the new version of Visual Studio, but our dev
engineer will keep improving them. And those comments and feedback from
commuinty are really important and valuable for our improvement. You're
welcome to submit them to the connect site:
>
#Visual Studio and .NET Framework - English

https://connect.microsoft.com/feedback/default.aspx?SiteID=210&wa=wsignin1.0

>
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:
msdnmg@microsof t.com.
>
=============== =============== =============== =====
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif

ications.
>
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://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
--------------------
Reply-To: "eschneider " <eschneider@com munity.nospam>
From: "eschneider " <eschneider@com munity.nospam>
Subject: Maintaining WS issues
Date: Thu, 17 Apr 2008 14:07:27 -0500
>
Just some common issues with WS:
>
Using custom objects: When objects change, seems you are always fixing
some
issue. Update references, which sometimes does not work.
>
Deployment:
Weird errors which take a while to fix because the error stink:
Forget to set ASP.NET 2.0="Parser Error Message: Could not load
type"
'*.Global' is ambiguous: it could come from assembly=I deleted the
following folders "Bin", "App_Code".
>
Different OS versions: have different deployment requirements/Security on
the box. (Think It could be easier, It's a public internet exposed
service,
or it's a corporate internal service)
>
Is the WS running? Where is it running? IIS or VS? what is the URL?
Where is the WS folder? Is it virtual?
They slow down VS solutions.
MS keeps changing how everything works together, all the time, making hard
to keep up with. (IIS vs. VS dev server, Security fixes)
>
Debugging is a pain, also seems you must step into them, to get it
working.
Also make sure you have it running first.
>
There is a lot more: VSS, and others I can't think of now.
>
WS Just seem to be a pain to maintain...
>
We have reached the point that we no longer use them unless we need to
interact with other technologies.
We tend to use mostly remoting now.
>
WCF seems to be better, but still seem it will suffers some of this.
>
We are currently using VS2005 pro.
>
Does anyone else have these issues?
>
Thanks,
Schneider
>
>
>
>
>

[Steven Cheng [MSFT]]

Re: Maintaining WS issues

Thanks for your reply Schneider,

Yes, WCF improve the distributed communcation on windows platform.
Actually, it tries best to combine all the features of former distributed
communication components such as .net remoting, webservice, MSMQ so as to
provide a uniform platform and programming interface.

Also, for hosting, it naturally support self hosting(in your own
application) in addition to IIS hosting. That also makes the deployment
more convenient. Anyway, welcome to post here if you have any further
questions.

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:
msdnmg@microsof t.com.

=============== =============== =============== =====
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif

ications.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Reply-To: "eschneider " <eschneider@com munity.nospam>
From: "eschneider " <eschneider@com munity.nospam>
References: <ujHWI5LoIHA.53 64@TK2MSFTNGP06 .phx.gbl>
<8#cHOfPoIHA.90 16@TK2MSFTNGHUB 02.phx.gbl>
Subject: Re: Maintaining WS issues
Date: Fri, 18 Apr 2008 10:18:58 -0500

Hello, Steven
Nice to hear back from MSFT.

It may be a lot better in VS2008 and/or with WCF. But we have not had a
chance to move to VS2008.
I have heard from people WCF is much better. The IIS version probably have
contributed to some of the problems, but then that part of the problems
with
webservices.

Thanks,
Schneider


"Steven Cheng [MSFT]" <stcheng@online .microsoft.comw rote in message
news:8%23cHOfPo IHA.9016@TK2MSF TNGHUB02.phx.gb l...

Hi eschneider,
>
Regarding on the issues you mentioned, some of them does exists when
dealing with some certain kind of projects in Visual Studio 2005. The
global classe issue maybe caused by a project converted from ASP.NET
1.1/VS 2003 project since the global class converted from original project
may confliect with a new one.
>
For the different deployment requirement, do you mean the IIS server? I
know that it may require different configuration for deploying web
application in IIS 5 and IIS 6 since they have different process model.
also, for the Visual Studio internal dev webserver, it is used for
developmente/test only, it can not be used for production(only accessible
from local machine).
>
I can understand your concerns that new features are kept being added into
Visual Studio and some functionality seems hard to use and may raise
problems. However, the visual tools and .net framework teams are really
working hard to address most of the issues. Actually most of the new
features also come from the community feedback and comments. Sure, there
may still occur problems in the new version of Visual Studio, but our dev
engineer will keep improving them. And those comments and feedback from
commuinty are really important and valuable for our improvement. You're
welcome to submit them to the connect site:
>
#Visual Studio and .NET Framework - English
>

https://connect.microsoft.com/feedba...&wa=wsignin1.0

>
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:
msdnmg@microsof t.com.
>
=============== =============== =============== =====
Get notification to my posts through email? Please refer to
>

http://msdn.microsoft.com/subscripti...ult.aspx#notif

ications.
>
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://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
--------------------
Reply-To: "eschneider " <eschneider@com munity.nospam>
From: "eschneider " <eschneider@com munity.nospam>
Subject: Maintaining WS issues
Date: Thu, 17 Apr 2008 14:07:27 -0500
>
Just some common issues with WS:
>
Using custom objects: When objects change, seems you are always fixing
some
issue. Update references, which sometimes does not work.
>
Deployment:
Weird errors which take a while to fix because the error stink:
Forget to set ASP.NET 2.0="Parser Error Message: Could not load
type"
'*.Global' is ambiguous: it could come from assembly=I deleted the
following folders "Bin", "App_Code".
>
Different OS versions: have different deployment requirements/Security on
the box. (Think It could be easier, It's a public internet exposed
service,
or it's a corporate internal service)
>
Is the WS running? Where is it running? IIS or VS? what is the URL?
Where is the WS folder? Is it virtual?
They slow down VS solutions.
MS keeps changing how everything works together, all the time, making hard
to keep up with. (IIS vs. VS dev server, Security fixes)
>
Debugging is a pain, also seems you must step into them, to get it
working.
Also make sure you have it running first.
>
There is a lot more: VSS, and others I can't think of now.
>
WS Just seem to be a pain to maintain...
>
We have reached the point that we no longer use them unless we need to
interact with other technologies.
We tend to use mostly remoting now.
>
WCF seems to be better, but still seem it will suffers some of this.
>
We are currently using VS2005 pro.
>
Does anyone else have these issues?
>
Thanks,
Schneider
>
>
>
>
>