Hi Phil,
Welcome to webservice newsgroup.
Regarding on the several questions you mentioned, here are some of my
understanding and suggestion:
1) Why, when I run code analysis do I get a source controlled files named
{guid}/codeanalysislog .xml
............... ............... ......
=============== =============== ==========
Not very familiar with Team System tools, however, as for the FxCop, it is
integrated with VS 2005 TeamSuite and Team Server so as to provide code
rules validating before checking in.. So I think the folder and output may
be something related to that setting. I'd suggest you try posting in IDE
related newsgroup since there may exists some experienced members there.
2) In .NET 1.1 web service classes where contained in a .NET namespace.
This is no longer the case in .NET 2 and code analysis complains about it.
I have excluded the FxCop warning but I was just interested to know why the
namespace was removed - and why FxCop still whinges.
=============== =============== ============
Yes, you're right, in .net 2.0/vs.net 2005, the ASP.NET web application or
webservice project no longer add a root namespace for all the pages or
component files created in them. Also, there is no precompiled asseblies
find. Because the ASP.NET 2.0 use the new compilation model (dynamic
compilation) which support source code (aspx) file all remain in
application folder so as to let the runtime dynamically compile them. Thus,
all the compiled classes(page classes) will be constructed under a certain
namespace (control by the internal compiler ....) , this is just how the
dynamic assemblies under Temporay ASP.NET folder in asp.net 1.1 be
constructed.... . And alternately, we can choose to precompile the
whole web application so that all the pages and components classes are
precompiled into assemblies before deployment, so that we only need to
deploy the aspx files (or asmx ...) to target site , also with the
precompiled assemblies.... in VS.NET 2005, the "Build---->PublishSite "
menu just do the work ... Anyway, the namespace behavior which
violate the fxcop rules does exist as you have met.
3) I'm using WSE3 and have built a WinForms client and web service using
............... ............... ....
=============== =============== ===========
Yes, we do have more convenient means to create server /client certificate
or any other type of certs though the WSE's sample certificates are also
created by makecert I think. I'm not sure whether there is another win2k
or win2k3 server box available in your environment. If so,we can install
the Microsoft windows certificate services on win2k or win2k3 server, then
we can use that server machine as a CA, we can request and get many kinds
of certificate through that server (through cert services manager or
through IIS web interface...) which is quite easy.....
4) In .NET 1.1 I have a setup program for installing my web service. In
............... ............... ...
=============== =============== ===============
For ASP.NET 2.0 project, as I've mentioned in 2), we can precompiled the
site through the "PublishSit e" function in VS2005 ide. We can put the
precompiled content into a local file sytem directory and all the things
there is what we need to deploy to target server. Then, we can make a
normal web application setup project to create virtual dir and deploy those
contents ....
In addition, the ASP.NET team is going to deliver a new "Web Deployment
Project" which provide much more features and control over creating ASP.NET
2.0 web application deployment package.... It's still under beta, but you
can get some info from it:
#Visual Studio 2005 Web Deployment Projects (Beta Preview)
http://msdn.microsoft.com/asp.net/re...p/default.aspx
Also, here is the blogs article from the web platorm & tools team's mgr ,
you can also get some of the background of this new project here:
http://weblogs.asp.net/scottgu/archi...06/429723.aspx
Hope helps. Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
