Master Pages
There is a new default master page. The new default masterpage has content place
holders in the head as well as in the body.
<%@ Master Language="C#"
AutoEventWireup="true"
CodeFile="MasterPage.master.cs"
Inherits="MasterPage"
%>
<!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Untitled
Page</title>
<asp:ContentPlaceHolder id="head" runat="server">
</asp:ContentPlaceHolder>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
</body>
</html>
Obviously, I don’t know the specific reasoning behind
it. However, it looks like it would
allow content in the head of a page to be individualized for a page. Cool trick.
Visual Studio 2008 Whitepaper
If you want to get the lowdown on Visual Studio 2008
straight from the guys that are writing it, check out the link below to Visual
Studio 2008 Whitepaper. I ran across it
while I was looking for other information.
http://www.microsoft.com/downloads/details.aspx?FamilyID=17319eb4-299c-43b8-a360-a1c2bd6a421b&displaylang=en
Source Control
I solved my problems with Visual Source Safe yesterday. I forgot to mention that I also have
Subversion working perfect. How? Well, we use RapidSVN for our main project
that John and I both work on. There is
no integration story there. RapidSVN
doesn’t plug into Visual Studio. So, it
all works and it works great. The key
part of the story to me is that the project files are compatible. That’s the real key.
Windows 2008 Server
I downloaded the express tools and installed them onto my
VPC running the June CTP of Windows 2008.
I installed Visual C# Express and Web Developer Express Beta2 onto the
product. The installs seemed to go well. I updated my code from the recent podcast and
it worked. Sorry, but I was too lazy to
sit through an entire install of VS.NET
into a VPC session. To get the
express versions of VS.NET 2008, go to: http://msdn2.microsoft.com/en-us/express/future/default.aspx
I opened my project from the
ASP.NET Podcast on Building an IIS7 HttpModule. Everything ran just like I expected it to.
.NET 2.0 Apps under Visual Studio 2008
Ok, this post continues to be the bible on how to get things working: http://blogs.msdn.com/webdevtools/archive/2007/07/30/using-vs-2008-to-target-asp-net-ajax-1-0.aspx I find that I keep going back to it over and over. It looks like there are several places where Visual Studio incorrectly identifies a .NET 2.0 Assembly as a .NET 3.5 Assembly. Remember, it is beta.
JSON Serializer
I download and extracted the AJAX Control Toolkit for .NET 3.5 this morning. I loaded it up into Visual Studio 2008 and compiled it. There are four warnings in it that are all the same. These warnings are: Warning: 'System.Web.Script.Serialization.JavaScriptSerializer.JavaScriptSerializer()' is obsolete: 'The recommended alternative is System.Runtime.Serialization.DataContractJsonSerializer.' The interesting thing is NOT the bug. The interesting part is that the new JSON Serializer is in the product. I had heard about this a long time ago that the JSON 1.0 Serializer was a temporary solution and that there was a better JSON Serializer coming from within the WCF team. I am guessing that this is it. Its great that using the original serializer results in code that is marked as obsolete.. That way, you don't get errors that things are broken when they really aren't and you get the gentile nudge to move your code forward.
Design & Source Views
The
Design/source views are not automatically kept in sync. The Design view changes are sent to the
source view, however, the changes in the source view are not automatically kept
in sync in the design view. However,
there is a small label you press to update the design view after changes in the
source view. The label alerts you when
things are out of sync.
On Thursday night, I posted to
one of the ASPInsider lists about a bug I think I have found when the split (design
and source) view is open. Within a
couple of hours, I had an email from PM in charge of VWD. Its awesome to see that there are people in
this world that really care about their products and have that amount of
energy. I'll post about this after I get
more info.