by community-syndication | Oct 10, 2008 | BizTalk Community Blogs via Syndication
Here is the latest in my link-listing series. Also check out my ASP.NET Tips, Tricks and Tutorials page and Silverlight Tutorials page for links to popular articles I’ve done myself in the past.
ASP.NET
-
Best Practices for Creating ASP.NET websites with IIS 6.0: Omar Al Zabir, author of the excellent Building a Web 2.0 Portal with ASP.NET 3.5 book, has a great article that details best practices to follow when setting up a site on IIS 6.0. Definitely worth reading and book-marking.
-
ASP.NET Continuous Integration and Deployment using CruiseControl.NET, Subversion, MSBuild and Robocopy: Omar Al Zabir has another great article – this time on implementing continuous integration with ASP.NET.
ASP.NET AJAX and jQuery
-
ASP.NET AJAX: Enabling Bookmarking and the Browser’s Back Button: Scott Mitchell continues his excellent series on ASP.NET AJAX and discusses how to add history points to an AJAX-enabled web page so that visitors can bookmark it, as well as to enable back/forward browser navigation. This is a new feature added to ASP.NET in .NET 3.5 SP1.
Microsoft Web Platform
Hope this helps,
Scott
by community-syndication | Oct 9, 2008 | BizTalk Community Blogs via Syndication
You probably know that if you want to make use of the fancy new .NET stuff, like ASP.NET AJAX in SharePoint 2007 sites, you have to make a bunch of modifications in the web.config of that site. You can do that the manual way, for example Mike Ammerlaan has described how you can enable ASP.NET AJAX 1.0 in SharePoint sites already a long time ago. Recently .NET 3.5 (including a new version of ASP.NET AJAX) became available, including the steps that you needed to go through to be able to enable it in SharePoint sites. You can check out Tobias Zimmergren’s post for example to get an idea.
Of course the manual approaches work, but it’s quite a lot of XML that you have to copy-and-past into the SharePoint web.config files. If you prefer an automated way to apply those changes, you can check out the SharePoint 2007 Features project on CodePlex. Over there you can find some feature that will apply the changes for you. But before you get too excited; make sure you test those features in your farms, because I’ve had some nasty experiences deploying them in SharePoint farms with multiple front-end web servers.
Today I’d like to introduce you the lazy way to apply the necessary changes for enabling .NET 3.5 (including the corresponding version of ASP.NET AJAX) in SharePoint 2007 sites. Actually it’s my lazy U2U colleague Lieven Iliano who thought me the trick, and I’ve been using it ever since in my classes and demos. The trick is to slightly abuse Visual Studio 2008 (just a little bit) here are the steps:
- Start Visual Studio 2008.
- Create a new dummy ASP.NET Web Application Project, and make sure you target the .NET Framework 2.0 (upper right dropdown of the New Project dialog). The name of this project is not important; you won’t need it anymore when we’re done.
- Copy the web.config of your SharePoint 2007 site, into the dummy Web Application project in Visual Studio.
- Open the Project Properties in Visual Studio (right click on the Project node in the Solution Explorer, and choose Properties; or in the Project menu, select WebApplicationX Properties).
- Select .NET Framework 3.5 in the Target Framework dropdown (select Yes in the confirmation dialog).
- Copy the web.config from the Web Application Project back to SharePoint.
That’s it; you now have copied the upgraded web.config to the SharePoint site! At this moment you’re ready to make use of all the fancy new .NET 3.5 stuff in your SharePoint 2007 site.
by community-syndication | Oct 9, 2008 | BizTalk Community Blogs via Syndication
Normal
0
false
false
false
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:”Times New Roman”;
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
It is great to find out people like the articles you write on your blog, and it’s even more fun when people actually contribute to your blog as well. That’s how I received an update to a blog post I wrote some time ago, about adding breadcrumb navigation to Application Pages. Bart Snyckers explained that the mechanism described in my post worked a little bit different if you want to add Application Pages to the Central Administration site. Bart doesn’t have a development blog yet (but he told me he’s working on one, and he’s running a photo blog already), so I’m posting Bart’s findings below. Thanks Bart!
Recently we also wanted to add breadcrumb navigation
to some Application Pages for SharePoint, which we were using in our Central
Administration, like the out-of-the-box Application Pages have. But it didn’t
worked out the way I wanted to. Google showed me the way to Jan Tielens’ blogpost
about Adding breadcrumb navigation to SharePoint Application Pages, The easy
way.
But after some research I found out that Application
Pages that you want to show in the SharePoint Central Administration Site should be placed in different folders than
normal Application Pages (in collaboration or publishing sites for example).
When you are building up your 12-hive structure you should use
12\TEMPLATE\ADMIN for the Application Pages (*.aspx) and sitemap
(admin.sitemap.*.xml) files, instead of the 12\TEMPLATE\LAYOUTS. If you mix up
the .aspx and .sitemap files between the ADMIN and LAYOUTS folder, the
breadcrumbs just don’t appear at all and if you place everything in the LAYOUTS
folder, the breadcrumbs don’t work like you expect them to do. Further you have
to reference the correct MasterPageFile from the ADMIN folder as well.
To deploy your feature and let SharePoint add the
sitemap entries, you can use the methods described in Jan’s article.Below you can find a small example to provision an
Application Page in the Operations tab in your Central Administration:
Application Page (.aspx), deployed to 12\TEMPLATE\ADMIN
<%@ Assembly
Name=”Microsoft.SharePoint,
Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”%>
<%@ Assembly
Name=”Example.SharePoint.CentralAdminApplicationPage,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=2de06805bd3065de”%>
<%@ Page
Language=”VB”
MasterPageFile=”~/_admin/admin.master”
Inherits=”Microsoft.SharePoint.WebControls.LayoutsPageBase”
%>
<asp:Content ID=”content1″
ContentPlaceHolderID=”PlaceHolderMain”
runat=”server”>
Central
Administration Application Page
</asp:Content>
<asp:Content ID=”content2″
ContentPlaceHolderID=”PlaceHolderPageTitle”
runat=”server”>
Central Administration Application Page
</asp:Content>
<asp:Content ID=”content3″
ContentPlaceHolderID=”PlaceHolderPageTitleInTitleArea”
runat=”server”>
Central Administration Application Page
</asp:Content>
Sitemap
(admin.sitemap.*.xml), deployed to 12\TEMPLATE\ADMIN
<?xml version=“1.0“ encoding=“utf-8“ ?>
<siteMap>
<siteMapNode title=“Central Administration Application Page“ url=“/_admin/CentralAdminApplicationPage.aspx“ parentUrl=“/_admin/operations.aspx“/>
</siteMap>
Feature (feature.xml)
<Feature xmlns=“http://schemas.microsoft.com/sharepoint/“
Id=“{25397E25-C142-423a-97D2-AEA7BA6C0879}“
Title=“Central Administration Application Page“
Description=“Enables the Central
Administration Application Page.“
Scope=“Site“
ReceiverAssembly=“Central Administration Application Page, …“
ReceiverClass=“Example.SharePoint.CentralAdminApplicationPage.FeatureHandler“>
<ElementManifests>
<ElementManifest Location=“customactions.xml“/>
</ElementManifests>
</Feature>
Customactions (Customactions.xml)
<Elements xmlns=“http://schemas.microsoft.com/sharepoint/“>
<CustomActionGroup
Id=“{79C8B7A7-E258-4835-B12D-D592F9CE100E}“
Title=“Central
Administration Application Page“
Location=“Microsoft.SharePoint.Administration.Operations“
Sequence=“100“ />
<CustomAction
Id=“{828008F8-20DB-4224-8D2C-A4826C66E874}“
Title=“Example Application Page“
GroupId=“{79C8B7A7-E258-4835-B12D-D592F9CE100E}“
Location=“Microsoft.SharePoint.Administration.Operations“
RequireSiteAdministrator=“TRUE“
Sequence=“10“>
<UrlAction Url=“/_admin/CentralAdminApplicationPage.aspx“/>
</CustomAction>
</Elements>
by community-syndication | Oct 9, 2008 | BizTalk Community Blogs via Syndication
According to the countdown timer at the PDC2008 site, the opening keynote is only 17 days away (at the time of writing). The previous PDC in 2005 was all about Office 2007 (including SharePoint) and Vista, but this time there didn’t seem to be a lot of Office/SharePoint content scheduled. Not that this is a bad thing; after 3 years of SharePoint teaching, coding and evangelizing, getting to know new technologies can be great. 🙂 I’m really looking forward to learn more about Live, Live Mesh, Cloud Services etc.
But if you check the PDC sessions now, you can find five SharePoint related sessions. For a nice summary check Paul’s blog post here. Hey there will even be a SharePoint booth! So I hope to meet you in LA!
by community-syndication | Oct 9, 2008 | BizTalk Community Blogs via Syndication
Sometimes in the BizTalk forums such questions appear.
“…I have been using event log to test variables. I was hoping there was a way to watch it process in VS like you can debug a forms app.”
There is a difference in the usual app and in the “BizTalk app“.
When you start usual app it is exactly this app and you could debug it. When you “start” the BizTalk app that could means *many* *instances* of this BizTalk app could works simultaneously.
With BizTalk you have an intermediate layer, the host. This host (actually it is a host instance but it doesn’t matter for this case) manages the app *instances*. It could start many app instances simultaneously and then dehydrate, rehydrate, stop, abort them without our intervention.
Ideally we need to attach a debugger to exactly one app instance (which one?) or create a debugger working with many app instances simultaneously.
It is one of the source of the complexity of debugging the BizTalk apps.
BTW What is a BizTalk application at all?
Please, let me know, what do you think.
by community-syndication | Oct 9, 2008 | BizTalk Community Blogs via Syndication
Something I’ve never come across before – which Host does a Dynamic Send Port use? There is no value displayed under the Handler column for a dynamic Send Port:
Also, when you look at the configuration for a dynamic Send Port (in this case a dynamic HTTP port), there is no drop-down option for the Handler:
So, […]
