Ich bin Aufstellung Sharepoint Services 3.0 an einem Windows Bediener 2003 SBS und stieß auf dieses Problem zufällig:

Problem:

Das Laufen lassen einiger Seiten im Willen der Sharepoint Services 3.0 gibt 403 verbotene Störung.

Nach etwas Googling würde die Lösung sein:

Workaround 1:

A) Temporäre Verlegenheit:

1. Benennen Sie das Web.config zu um  irgendein anderer Dateiname.
2. Versuch, der wieder die 403 verbotene Seite zugänglich macht.
3. Benennen Sie zurück zu Web.config um

B) Dauerhafte Verlegenheit:

Dieses wird durch ein Microsoft .NET Update des Rahmens 2.0 verursacht. Uninstall der Flecken KB928365.

Schicken Sie uns einige Anmerkungen, wenn dieses arbeitet!

BARCELONA, Spanien - November. 5, 2007 - Heute während der Ansprache an Microsoft TechEd Entwicklern 2007, S. „Soma“ Somasegar, korporativer Vizepräsident der Entwickler-Abteilung bei Microsoft Corp., verkündet, daß Microsoft Sichtstudio 2008 und den .NET Rahmen 3.5 Ende November 2007 freigibt. Sichtstudio 2008 und der .NET Rahmen 3.5 ermöglichen Entwicklern auf allen Niveaus, verbundene Anwendungen schnell zu verursachen, die unwiderstehliche Benutzererfahrungen für Windows Vista, Windows Bediener 2008, das Microsoft Officesystem 2007, die beweglichen Vorrichtungen und das Netz anbieten. Vorgestellte Pläne des Soma auch, zum der neuen Gelegenheiten für Sichtstudiopartner, sowie zu öffnen, neue Werkzeuge und Betriebsmittel für Entwickler, einschließlich eine erste Gemeinschaftstechnologie-Vorbetrachtung (CTP) des Microsoft Synchronisierung Rahmens und neue Fähigkeiten für Popfly Forscher zu liefern.

„Die in hohem Grade Sozial- und Sichtnatur des Netzes hat grundlegend geändert, was Benutzer von allen Anwendungen, die sie auf einwirken, unabhängig davon erwarten, ob es auf Kundeeinfassungen Web site oder Windows reiche Klient Anwendung ist, oder eine desktop Geschäft Anwendung, die mit Microsoft Office errichtet wurde,“ sagte Somasegar. “Traditionally, organizations have been hard pressed to deliver the richer, more connected applications and services they need to boost productivity, drive revenue and stay ahead of the competition. With Visual Studio 2008 and the .NET Framework 3.5, it is easy for developers to use the skills they already have to build compelling applications that take advantage of the latest platforms.”

FWBS Ltd., Xerox Corp., Dell Inc. and K2 are just a few of the early adopter customers

Few days ago, I shared about how to upgrade your ASP.NET 1.1 to ASP.NET 2.0, this time I am going to discuss about enabling ASP.NET AJAX v1.0 to your existing Web Site or Web Application.

1) You have to downlaod and install the ASP.NET 2.0 AJAX Extensions 1.0. Here
2) You may download and extract the ASP.NET AJAX Control Toolkit. Here

After install it, you will found out that you may create AJAX Enabled Web Application when creating new projects(Web Site or Web Application). You may also found out that there is a new tab called “AJAX Extensions” in Toolbox. If you have extracted the ASP.NET AJAX Control Toolkit, you may do the following,

1) Create new tab called “AJAX Control Toolkit”;
2) Right click under the created tab and click on “Choose Items…”;
3) Click “Browse…” and browse to the folder which you extract the ASP.NET AJAX Control Toolkit, and then browse to “~\SampleWebSite\Bin\” and select AjaxControlToolokit.dll
4) Now you will see a lot of controls which you are ready to use. You may browse and view the “Toolkit Live” to get the sample and idea on the controls.

You are now ready to build your AJAX web site or web application. However, if you have any existing ASP.NET 2.0 Web Site or Web Application, you do the normal action to write AJAX, you will found out that the AJAX is not working in your existing Web Site or Web Application. You have to do the following in order to let

As you might already know, the VS2008 VPC will be expired on Nov 1st, the VSTS team is going to release a new VPC with updated expiration date.  Detail in below,

As the final act in our saga of expiring VPCs, I’m happy to announce that we’ve reissued VPCs for VS2008 Beta2 with an updated expiration date.  You can find the updated links on the VS2008 download page:

• Visual Studio Team System 2008 Beta 2 Team Suite VPC
• Visual Studio Team System 2008 Beta 2 Team Suite & Team Foundation Server VPC

Thanks to everyone that has helped us get the word out about this situation and please accept our apologies for any inconvenience this might have caused you.  Needless to say, we’re taking steps now to ensure that we don’t make this particular mistake again.

Source from Jeff Beehler’s Blog — VS2008 Beta2 VPCs re-released

Last time, I speak in Hong Kong .NET UserGroup Monthly Gathering in 2007 Sept right after MSDN Seminar, the topic was “Experience Sharing: Upgrading ASP.NET 1.x –> 2.0 –> AJAX”. Well, I also promised that i will blog about it. Actually, it is nothing new and it is nothing special. I just shared my experience on how I upgrade ASP.NET 1.1 to 2.0 and how to enable AJAX.

First, I am not sure if you know that, in .NET framework 2.0, there is 2 types of Web Projects, ASP.NET 2.0 Web Site and ASP.NET 2.0 Web Application. You may refer to the following link for more information if you would like to read more.

Introduction to Web Application Projects
http://msdn2.microsoft.com/en-us/library/Aa730880(VS.80).aspx

If you are going to upgrading your existing ASP.NET 1.x project, you should choose to be using ASP.NET 2.0 Web Application project. This is the message from one of ScottGu’s blog, Tutorial on VB and C# are also mentioned.

“Because the VS 2005 Web Application Project model has the same conceptual semantics as the VS 2003 Web Project Model, it also makes migrating VS 2003 web projects very, very easy – with zero/minimal code changes required. To learn how to automatically upgrade a VS 2003 web project using this option, please review these VB and C# tutorials that walkthrough the VS 2003 to VS 2005 upgrade process step-by-step.”

However, if you want to