Details of WPF/E were announced at MIX06. All I can say is
go checkout http://blogs.msdn.com/mharsh/archive/2006/03/23/559106.aspx
From that page . So what is WPF/E? It is a
cross-platform, cross-browser web technology that supports a subset of WPF
XAML. WPF/E also has a friction-free install model and the download size
we’re targeting is very small. WPF/E supports programmability
through javascript for tight browser integration. The WPF/E package also
contains a small, cross platform subset of the CLR and .NET Framework that can
run C# or VB.NET code. Yes, we are bringing C# programming to the Mac
We are planning Devdays right now. The plan is to deliver 1
track on security and another track focused on introductions to WinFX (WCF,
WPF, WF). Right now it looks like the sessions might not be aligned (i.e
session start and end times between tracks could be different)
Comments, moans? I would be keen on your feedback as well as
what you think developers in general (those who might not read blogs etc) will
want.
You have one public holiday and a whole bunch of new stuff
come out. I guess with MIX, Office Developer Conference and the Game Developer
Conference at the same time that was bound to happen. Bill Gates even managed
to keynote MIX on Monday and Office DevCon on Tuesday. Some update
1) The Atlas
Mar CTP is available. You can Go-Live with these bits
2) A new build of IE7 – Beta 2 Preview is available
3) A CTP of VSTO v3 is available
. As per the website, The Visual Studio
Tools for Office "v3" CTP gives developers who are using the
Microsoft Office 2007 beta 1 technical refresh an early glimpse at some of the
key new features and feature directions in the area of Office programmability.
These features include extensibility of the new Office UI, the new Office Open
XML file formats, and support for customizable application-level task panes
across Office applications. The next version of Visual Studio Tools for Office
is designed to help developers take advantage of the new capabilities in Office
2007, as well as to provide additional infrastructure to ensure Office
solutions created with managed code run more reliably, efficiently and securely
4) The Windows
Developer Live Center went live (excuse the pun J )
5) Managed Code will be supported on the Xbox and the XNA
Framework was unveiled. From http://www.microsoft.com/xna/
The XNA Framework is an exciting new
development and execution environment which will allow game developers to more
easily create games which run on the Microsoft Windows and Xbox 360 platforms.
It is being designed with a unified set of class libraries which will allow for
maximal re-use of code and assets across target platforms. A custom version of
the Common Language Runtime is being built to enable the execution of managed
code on an Xbox 360,
6) Related to above. The XNA Build Mar CTP is available
7) http://openxmldeveloper.org/default.aspx
was announced at the Office Developer Conference.
As far I know both the Office and MIX keynotes should be
available – I need to find them and check them out J
We just released MMC 3.0 for Windows Server 2003. You can download it from here. There is also an XP Version available
You can then visit MSDN to create a simple Hello World Snap In. Nice. It would be cool if there was a starter kit, project template and some snippets but this is still great. Should make the tasks on creating management consoles a lot easier.
I came to work this morning and to my pleasant surprise our internal servers had already downloaded the final bits of Team Foundation Server. So I decided to upgrade (I had the RC bits on this machine). I decided to just get rid of the old stuff and hence removed Team Build, Team Explorer, TFS and WSS. I then went into SQL Management Studio and got rid of the WSS and TFS databases (not removed during uninstall).
I then reinstalled WSS (in server farm mode!) and started to install TFS. A few days ago I stopped a bunch of SQL Services and IIS etc when playing around with some stuff. The install picked this up and gave me 1 warning and a few errors. Most of the errors were around some services not started. 1 error was about not having a hotfix installed. I installed the hotfix and for safety sake (and I think I had a pending reboot anyway) I rebooted.
I then installed in single server mode. The TFS install went through just fine now (1 warning about my CPU speed L). I then installed Team Explorer and then Team Build (note that for Team Build you must go to the build directory and install. There is no option from the menu). To test I created a new project based on the MSF Agile process. This took only about 4 minutes and went through just fine.
This machine has had tons of betas and uninstalls/reinstalls so it was great to see the experience being so smooth. Kudos to the TFS Setup team for making the experience great. I remember installing the first beta and it was a mission. The whole process took about 90 minutes (and I got to catchup on email and write this blog entry at the same time)
Only problem now is I had configured and done some investigation for a couple of customer sessions, so I will need to do that again.
Rick Laplante made the announcement at the SD West conference yesterday (Thurs). It should take a few days to propagate to MSDN. See Soma?s blog for a bit more info on TFS
I had this issue for awhile on my machine (same one with the
earlier betas installed). When I try and add a new project item to a C# or
VB.NET Project I see nothing listed. I need to click the Project Items node in
order for me to see the templates. Turns out that if I simply delete the Local
Project Items (LocalProjectItems) folder in
<Program Files>\Microsoft Visual Studio
8\VB\VBProjectItems and <Program Files>\\Microsoft Visual Studio
8\VC#\CSharpProjectItems, my irritating problem went away
One of the questions I was asked was whether you can use just the source control features of VSTS, and not any of the other features (work item tracking, reporting, portal etc)
The answer is NO and YES.
No , When you install VSTS you have to configure Windows Sharepoint Services, Reporting Services etc. You can not indicate that you only want the source control features
Yes , When creating the project you can create all the artifacts but just use source control. This is not optimal.
One of the nice features of TFS is the ability to customize the process templates. I played with this a bit and modified the ProcessTemplate.xml file. See below (I used the MSF Agile as the basis). In this case you will notice that I have removed some of the plugins.
I uploaded this and created a new project based on this template. It ran really fast. No reports, work items or portal was created. When I right clicked work items there was no option to create a work item. I did one basic test of creating a Windows app and adding it to the source repository. The checkin worked fine. I have not done a full test of this so there could be some things I missed.
Having said all of that. The value of Team System really lies in the integration between the portal, reporting, work items etc. So I would not normally recommend this.
<?xml version="1.0" encoding="utf-8" ?>
<ProcessTemplate>
<metadata>
<name>Demo</name>
<description>Demo</description>
<plugins>
<plugin name="Microsoft.ProjectCreationWizard.Classification" wizardPage="false"/>
<plugin name="Microsoft.ProjectCreationWizard.Groups" wizardPage="false"/>
<plugin name="Microsoft.ProjectCreationWizard.VersionControl" wizardPage="true"/>
</plugins>
</metadata>
<groups>
<group id="Classification"
description="Structure definition for the project."
completionMessage="Project Structure uploaded.">
<dependencies>
</dependencies>
<taskList filename="Classification\Classification.xml"/>
</group>
<group id="Groups"
description="Create Groups and assign Permissions."
completionMessage="Groups created and Permissions assigned.">
<dependencies>
<dependency groupId="Classification" />
</dependencies>
<taskList filename="Groups and Permissions\GroupsandPermissions.xml" />
</group>
<group id="VersionControl"
description="Creating version control."
completionMessage="Version control task completed.">
<dependencies>
<dependency groupId="Classification"/>
<dependency groupId="Groups"/>
</dependencies>
<taskList filename="Version Control\VersionControl.xml"/>
</group>
</groups>
</ProcessTemplate>
If you are running XP and getting the error ?Insufficient System Resources Exist to Complete the API? when you try to hibernate then there is good news (or most good news). The good news is that a fix is available. See http://support.microsoft.com/Default.aspx?kbid=909095 for information.
The not so good news L
1) You need to phone PSS (locally 0860 22 55 67) to get the fix. There should be no charge but the download is not available publicly
2) The problem happens on Windows Server 2003 as well and there is no hotfix yet for WS03. That is too bad for me. I can understand why it is not yet available as not too many people hibernate their servers but with me running VSTS etc on my laptop I would have liked the fix for my machine.