乐趣为王

下班回来就看见这样的消息，赶快下载了一个安装上。虽说IE7对于我常用的GreenBrower来讲，并没有新鲜的功能，但是对于IE6来讲还是有很大的进步的。个人觉得有了IE7以后，XP SP2至少可以用到SP3；而没有IE7的Vista和XP比就真没什么实用的功能提升了……

我不是用IE7早的人，我什么也不说了，看人家写的教程去了

连接：
http://download.microsoft.com/download/4/1/8/418981A4-6EF9-4DE6-BEFC-1A53E886CB62/ie7-windowsxp-x86-chs.exe
http://download.microsoft.com/download/8/8/d/88dc5518-0a4d-4912-a8a3-a0fcb6fb657f/IE7-WindowsServer2003-x86-chs.exe

这篇文章来自ReportingService For SQL Server 2000的安装说明文件。

On Windows Server 2003, if you install Reporting Services with Windows SharePoint Services, you need to follow some basic steps in order for your system to function properly. To enable a side-by-side installation of Reporting Services and Windows SharePoint Services, perform the following steps.

1. While installing Reporting Services, you may experience activation failures. Ignore any activation errors that occur.
2. Add the Reporting Services virtual directories to the Windows SharePoint Services list of exclusions. If you installed Reporting Services using the default virtual directories, run the following at the command prompt:
   STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion
   and
   STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion
3. Next, increase the trust level to full trust in the Report Server and Report Manager Web.config files. By default, the Report Server Web.config file is located at C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer. The Report Manager Web.config file is located at C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager. You can increase the trust level by modifying the trust level element of the system.web configuration element from <trust level="RosettaSRV" originURL=""/> and <trust level="RosettaMGR" originURL=""/> to the following:
   <trust level="Full" originUrl="" />
   You must make the trust level entry in both Web.config files. Modify only the trust level element of system.web. Do not modify the similarly named trustlevel element of the security policy configuration element.
4. Add the following under the HttpModules configuration element of the SharePoint Web.config file if it does not already exist. By default, the SharePoint Web.config file is located at C:\Inetpub\wwwroot.
   <HttpModules>
      <add name="Session" type="System.Web.SessionState.SessionStateModule"/>
   In addition to adding the session state module, you must also enable session state for the pages element by changing the enableSessionState attribute from false to true. The entry in the configuration files should look like the following:
   <pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" />
5. From the Internet Information Services (IIS) Manager, ensure that the report server is in an application pool that is separate from the SharePoint server. The report server management user interface, Report Manager, can remain in the same application pool to which it was originally installed. To assign the report server to a separate application pool, you must first create a new application pool. After you have created a new application pool, expand Web Sites, expand Default Web Site, right-click the report server virtual root that you created during setup (the default is ReportServer), and then click Properties. From the Application pool drop down, select the newly-created application pool. For more information about application pools, see your Internet Information Services documentation.
6. Finally, use the rsactivate utility to activate the local instance of Reporting Services. You need to install Administrative Tools and Utilities as part of Reporting Services setup in order to use the rsactivate utility. By default, rsactivate is located at C:\Program Files\Microsoft SQL Server\80\Tools\Binn. If you installed your report server to the default location, run the following at the command prompt:
   rsactivate -c "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config"

今天晚上回来不是特别的忙，仔细扒了扒MSDN Blogs里面的SharePoint相关的Blog，几个连接大家分享。

在几个Blog里面都看到了MOSS和WSSv3的最新版SDK发布到MSDN上面了，但是现在只能在线阅读，离线的CHM版本还停留在Beta2TR阶段。对于两者的区别还不清楚，先把连接给大家列出来吧：
WSS SDK here
MOSS SDK here

在MOSS2007产品组的Owen Allen 的Blog上面看见了他发布的四个连接，分别是WSSv3和SharePoint2007的单机和服务器场部署指南。这些文章好像是这两天才发布到TechNet上面的。先记录在案：
WSS – Single Server
WSS – Server Farm
MOSS – Single Server
MOSS – Server Farm

现在还没有中文的MOSS版本出现，所以我想我会先翻译WSS的版本，估计到时候会配上中文版的WSSv3的截图，大家为我祈祷吧！

把Blog的程序升级到了DasBlog1.9。把页面的Theme也换了。

DasBlog的升级没感到什么太大的变化，新的Theme还是不错的，界面清新，最主要的一点是速度快。我是忍受够了那个名叫dasBlog的Theme。

随着Blog程序的升级，速度的加快，Blog的更新也要加快了。

今天上午WSS3.0提供下载了，中文版也一同发布了。正好手头有一个.NET Framework 3.0的虚拟机，立刻就把这个东西装上了。感觉不错。安装过程很顺畅，没有BETA2时候安装不长的问题了。安装过程和MOSS2007 BETA2的安装过程很像，但是缺一些东西，估计这些就是区别。

现在发现的和MOSS2007的区别是MOSS2007独立模式安装的时候，会安装一个SQL Server 2005的Express版的引擎，这个引擎可以通过标准的SQL Server 2005的管理工作室进行管理。而WSS3.0独立模式安装的时候，数据库引擎是一个SQL Server 2005的嵌入版。在使用SQL Server 2005的管理工作室的实例列表当中可以看到他创建的实例，但是不能连接，提示“引擎不提供远程连接功能”。估计这就是SQL Server 2005的Express版和嵌入版的区别所在，还有就是嵌入版默认的安装位置是%windir%\SYSMSI目录。我是第一次知道有这样一个SQL Server 2005的版本存在，需要研究一下这个版本的特性。

WSS3.0的内存消耗堪称一流，我的机器上除了企业版的SQL Server 2005以外，就是这个WSS3.0和其附带的嵌入版的SQL Server 2005了，这个时候内存占用达到了850兆。不知道MS怎么想的，这个内存的消耗是在太大了，虽然现在内存便宜，工作组服务器也不贵，但是这样的内存消耗也太大了点…在虚拟机里面有点实在吃不消了。

在前两天随.NET Framework 3.0一起发布的VS.NET 2005的WSS3.0扩展是个很不错的东西，除了带有Webpart模板意外，还能创建站点定义。这个可以看看陈曦的blog里面的描述。

前面一段时间我的blog里面的文章少了，但是随着.NET Framework 3.0和MOSS2007的到来，各样的文章会如潮涌一样上来的…敬请关注

虽然NetFx3的网站上的连接还没有变更过来，但是微软网站里面确实提供下载了，更新日期2006年11月6日，连接如下：
x86 full package http://go.microsoft.com/fwlink/?LinkId=70848

SDK也发布了，更新日期2006年11月3日，连接如下：
Full Image http://download.microsoft.com/download/1/b/3/1b3f749d-e215-482c-a004-5d9c26c75c92/6.0.6000.0.0.WindowsSDK_Vista_rtm.DVD.Rel.img

Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP，更新日期2006年11月6日，连接如下：

http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=F54F5537-CC86-4BF5-AE44-F5A1E805680D&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2ff%2ff%2f0%2fff0433fe-733c-4ff4-89aa-c77ff587f388%2fvsextwfx.msi

Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation)正式版，更新日期2006年11月6日，连接如下：
http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=5D61409E-1FA3-48CF-8023-E8F38E709BA6&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f9%2f6%2fc%2f96cfedbc-89ed-4b57-9cac-27ecad390149%2fVisual+Studio+2005+Extensions+for+Windows+Workflow+Foundation+(EN).exe

Visual Studio 2005 extensions for WSS 3.0正式版，更新日期2006年11月6日，连接如下：
http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=19F21E5E-B715-4F0C-B959-8C6DCBDC1057&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2fe%2f8%2fa%2fe8aa8476-5af6-4f38-aed2-0247a99d2bc6%2fVSeWSS.msi