Posted from BLInk!
Monthly Archives: August 2005
Are you going to PDC?
PDC is getting closer and you can feel the level of excitement in the blogosphere. Once again, the event has sold out. This always amazes me — that Microsoft could sell out events with over 10,000 attendees. This has been happening for PDC and TechEd for a few years now that I know of [read more…]
[A DevLife post]
www.acehaid.org
The developer, the project manager and the business unit veep – a conversation on product roll-out
Camey relays a conversation that may bring [un]fond memories to many developers… but go ahead, torture yourself anyway and read it.
www.acehaid.org
Go Vote for my PDC Birds of a Feather Sessions
I JUST submitted two BOF sessions, so I don’t know when they will show up on the list. Voting ends Monday, so go vote!
TabletPC: If you build it, will they come?
The TabletPC SDK has been around for a few years now and has some great innovations for developers to write really cool inkable applications. But where are our users? This BOF is a chance for Tablet PC Developers to get together to discuss their shared passion for this incredible technology and their shared frustrations with the slow growth of the Tablet PC market.
Going Solo
Have you ever thought of going independent? This session aims to bring together independent developers with those who have toyed with the idea to share advice, lessons learned and more.
www.acehaid.org
Women in Technology Panel at PDC
www.acehaid.org
WSE3 Beta 1 Release Notes
Since I didn’t see the release notes are not on the website for WSE3.0 Beta1, I thought I would put the key bits here.
Main Features Updated from the July CTP Release
- Wsewsdl3.exe can now produce ASP.NET proxy clients from an ASP.NET Web service over TCP using the /type:
parameter. This setting determines the default proxy type to generate. Choose from ‘webClient’, ‘soapClient’. If you choose webClient, a proxy class deriving from WebServicesClientProtocol will be generated, otherwise, a proxy class deriving from SoapClient will be generated. The soapClient is the default. - The policy framework has new assertions for <requireSoapHeader> and <requireSoapAction> which enforce constraints on the received messages to require that either a SOAP header is present or a SOAP action is present. See the product documentation for more details. The schema for the WSE policy, wsePolicy.xsd, can be found in this directory C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas after WSE 3.0 is installed.
- WSE generated proxies have the same asynchronous pattern as ASP.NET 2.0 generated proxies.
- More detailed tracing when a policy fails during the processing of a message.
- The SoapHttpRouter class now works with the policy framework to enable you to secure messages with policy files. See the quickstart samples for an example.
Known Issues
- The WSE Settings may not be integrated with Visual Studio 2005. This occurs if you install Visual Studio 2005 and then install WSE 3.0 Beta 1 without first having started Visual Studio 2005. Ensure that you start Visual Studio 2005 before installing WSE 3.0 Beta 1. Alternative you can use the Visual Studio 2005 Add-in Manager available from the Tools menu item to manually install the WSE 3.0 Settings tool.
- WSDL files produced by the Windows Communication Foundation (formally codenamed “Indigo”) Beta 1 cannot be consumed by WseWsdl3.exe
- Using WSE with Web services hosted in ASP.NET, SOAP section 5 encoding does not work. Set the Web service to use literal encoding instead.
- With Microsoft Windows 2003 Server SP1, all Web services that run under the Network Service account cannot write WSE diagnostic trace files. To enable these services to write diagnostic files, either add write access permission for the Network Service account to the directory where the diagnostics files are being written or alternatively run the service under an account which has write access privileges.
- WSE 3.0 and the Windows Communication Foundation (formally codenamed “Indigo”) Beta 1 cannot be installed on the same machine as they use different versions of the .NET Framework.
- Wsewsdl3.exe cannot produce ASP.NET proxy clients when just the .NET Framework Runtime is installed on the machine. The .NET Framework SDK is required.
www.acehaid.org
MSDN Subscription downloads scheduled outage
Because I have been watching the download site like a hawk for the August bits of VS2005, I noticed this and thought I would share:
Outage Update: The MSDN Subscriber Downloads site will be undergoing a system upgrade on 25 August 2005 starting at 5:00 PM Pacific Time. The Subscriber Download site will be unavailable and any in-progress downloads may not complete successfully. Our expected outage time is 2 hours.
www.acehaid.org
WSE 3.0 Beta is out
The WSE 3.0 Beta was released today (or was that yesterday). It requires the August CTP of VS2005. Too bad I’m still waiting for the VSTS version of that since only the VS2005 Express bits are available for August CTP.
[thanks Nathan]
www.acehaid.org
QA Testing for Windows 95
www.acehaid.org
DataSet enhancements in ADO.NET 2.0
I recently received my TechEd 2005 conference DVDs which allow me to now catch up on many awesome sessions I was not able to attend while I was there. One session in particular that I just watched which is filled with great prescriptive information – not just how to , but when and why – is “DAT421: Client and Middle Tier Data Caching with SQL Server 2005” by Pablo Castro and Steve Lasker. One of the gems in there is this slide by Pablo, who is the PM on the ADO.NET team. [read more]
[A DevLife post]
www.acehaid.org