Mads Nissen
backlog on sharepoint, crm, office, .net development, architecture and more..
-
QueryStringPageViewer WebPart for Sharepoint
/// <summary> /// Mads Haugbø Nissen 2003(c) /// Objectware AS /// Norway /// /// http://weblogs.asp.net/mnissen /// /// The QueryStringPageViewer provides the same functionality as the regular PageViewerWebPart /// but allows providing a selection of querystring parameters from the page that hosts this webpart /// to the page viewed in the QueryStringPageViewer. /// </summary> [DefaultProperty("ContentLink"), ToolboxData("<{0}:QueryStringPageViewer runat=server></{0}:QueryStringPageViewer>"), XmlRoot(Namespace="http://www.objectware.no/Lawyer/Sharepoint/Webparts/QueryStringPageViewer")] public class QueryStringPageViewer : Microsoft.SharePoint.WebPartPages.WebPart { private string _contentLink = ""; [Browsable(true)] [Category("Content")] [DefaultValue("")] [WebPartStorage(Storage.Shared)] [FriendlyName("The url of the content to show.")] [Description("Supply Querystring params to be passed like this: Page.aspx?Param1&Param2&Param3")] public string ContentLink { get { return this._contentLink; } set { this._contentLink = value; } } protected string BaseUrl { get { int endIndex = this.ContentLink.IndexOf("?"); if(endIndex != -1) return this.ContentLink.Substring(0, endIndex + 1); else return ""; } } /// <summary> /// Render this Web Part to the output parameter specified. /// </summary> /// <param name="output"> The HTML writer to write out to </param> protected override void RenderWebPart(HtmlTextWriter output) { string url = this.UrlWithQueryStringGet(); if(url.Length > 0) { string name = "QueryStringPageViewer_" + this.UniqueID; output.AddAttribute(HtmlTextWriterAttribute.Id, name, false); output.AddAttribute(HtmlTextWriterAttribute.Name, name, false); output.AddAttribute(HtmlTextWriterAttribute.Width, "100%", false); output.AddAttribute(HtmlTextWriterAttribute.Height, "100%", false); output.AddAttribute(HtmlTextWriterAttribute.Height, "100%", false); output.AddAttribute(HtmlTextWriterAttribute.Src, url, false); output.AddAttribute("ddf_src", url, false); output.AddAttribute("frameBorder", "0", false); output.RenderBeginTag(HtmlTextWriterTag.Iframe); output.RenderBeginTag(HtmlTextWriterTag.Div); output.Write("IFrames not supported by this browser"); output.RenderEndTag(); output.RenderEndTag(); } else { Control c = new LiteralControl(string.Format("To link to content, <a href=\"javascript:MSOTlPn_ShowToolPaneWrapper('{0}','{1}','{2}');\">open the tool pane</a> and then type a URL in the ContentLink text box with QueryString parameters formatted like this: 'Page.aspx?Param1&Param2'.", 1, 129, this.ID)); c.RenderControl(output); } } private ArrayList QueryStringKeysGet() { int startIndex = this.ContentLink.IndexOf("?"); ArrayList queryStrings = new ArrayList(); if(startIndex > -1 && this.ContentLink.Length > startIndex + 1) { string queryStringRaw = this.ContentLink.Substring(startIndex + 1); if(queryStringRaw.IndexOf("&") != -1) { string[] tokens = queryStringRaw.Split(new char[]{'&'}); for(int i = 0; i < tokens.Length; i++) queryStrings.Add(tokens[i].ToLower()); } else { queryStrings.Add(queryStringRaw.ToLower()); } } return queryStrings; } protected virtual string UrlWithQueryStringGet() { ArrayList queryStringsToPass = this.QueryStringKeysGet(); string url = this.BaseUrl; for(int i=0; i < Page.Request.QueryString.Count; i++) { string queryStringKey = Page.Request.QueryString.Keys[i]; string queryStringValue = Page.Request.QueryString[i]; if(queryStringsToPass.IndexOf(queryStringKey.ToLower()) != -1) { url += queryStringKey + "=" + queryStringValue + "&"; } } url = url.TrimEnd(new char[]{'&'}); return url; } }
<?xml version="1.0" encoding="utf-8"?> <WebPart xmlns="http://schemas.microsoft.com/WebPart/v2" > <Title>QueryStringPageViewer</Title> <Description>Passes querystring parameters to the page in the viewer.</Description> <Assembly>Objectware.Lawyer.Sharepoint</Assembly> <TypeName>Objectware.Lawyer.Sharepoint.WebParts.QueryStringPageViewer</TypeName> <!-- Specify initial values for any additional base class or custom properties here. --> <ContentLink xmlns="http://www.objectware.no/Lawyer/Sharepoint/Webparts/QueryStringPageViewer"></ContentLink> </WebPart>
-
Using an XmlPublisher in the ExceptionManagement ApplicationBlock
I've been using the Microsoft ExceptionManagement ApplicationBlock and I spent some time creating a nice ExceptionXmlPublisher because the one described in the docs has some flaws. Using the xml publisher removes the need to run the EventLog installer to be able to create the eventlog. Having the exceptions in Xml also works nicely in a distributed environment, and with continous integration. I will soon create an XSLT stylesheet to integrate the current runtime exceptions into my CruiseControl.NET dashboard, so developers can monitor what's going on during execution on the development testserver.
-
ExceptionXmlPublisher for Microsoft.ApplicationBlocks.ExceptionManagement
using System; using System.Xml; using System.Collections.Specialized; using System.IO; namespace Microsoft.ApplicationBlocks.ExceptionManagement { /// <summary> /// Summary description for ExceptionXmlPublisher. /// </summary> public class ExceptionXmlPublisher : IExceptionXmlPublisher { void IExceptionXmlPublisher.Publish(XmlDocument ExceptionInfo, NameValueCollection ConfigSettings) { string filename; if (ConfigSettings != null) { filename = ConfigSettings["fileName"]; } else { filename = @"C:\ErrorLog.xml"; } XmlDocument xmlTarget = new XmlDocument(); FileStream fs; if(File.Exists(filename)) { fs = File.Open(filename, FileMode.Open, FileAccess.Read); try { xmlTarget.Load(fs); } catch { xmlTarget = new XmlDocument(); xmlTarget.AppendChild(xmlTarget.CreateXmlDeclaration("1.0", "UTF-8", "yes")); xmlTarget.AppendChild(xmlTarget.CreateElement("RuntimeExceptions")); } finally { fs.Close(); } } else { xmlTarget.AppendChild(xmlTarget.CreateXmlDeclaration("1.0", "UTF-8", "yes")); xmlTarget.AppendChild(xmlTarget.CreateElement("RuntimeExceptions")); } XmlDocumentFragment docFrag = xmlTarget.CreateDocumentFragment(); docFrag.InnerXml = ExceptionInfo.OuterXml; XmlNodeList stackTraceNodes = docFrag.SelectNodes("//StackTrace"); foreach(XmlNode node in stackTraceNodes) { node.InnerXml = "<![CDATA[" + node.InnerXml + "]]>"; } xmlTarget.DocumentElement.AppendChild(docFrag); fs = File.Open(filename, FileMode.Create, FileAccess.Write); try { xmlTarget.Save(fs); } catch {} finally { fs.Close(); } } } }
-
Navision Axapta COM Connector
I've been working quite a lot with integration between Sharepoint and the Navision Axapta COM Connector lately and have guts to spill. There is so much guts though, that I want to do a tiny poll before embarking on this article.
-
Dynamic creation of Sharepoint WSS Sites
Getting the most out of a Sharepoint project depends heavily on the degree of usage of the Sharepoint Portal Site and Windows Sharepoint Services architecture.
-
Developers are Athletes, Architects are Coaches/Managers/Trainers
Kris Syverstad writes about how developers resemble athletes. Reading his post I felt almost as Kris had been reading my final term paper in methodology from last spring where I used the exact same analogy. I wrote about developers as athletes in the context of higher learning, and how some students are suited for the extreme and some are more comfortable with the regular amount of training.
-
TechEd Europe 2004 I'll be there
Then I finally got to go. And this time I actually have a valid ticket for the sessions! Thanks to Patrice for the logo:-)
-
PageViewer WebPart and QueryString parameters
There has been dicussion (and people have noticed) about a Connected Page Viewer Webpart. There are several viable approaches to this scenario. One is to use cross-page connected webparts, but those require FrontPage interaction. There has been suggested that inheritance can be used from the PageViewerWebPart. Good luck: It's sealed.
-
Setting WebPart Properties through the WSS Web Services API
-
Managing Outlook / Exchange content in Sharepoint
There are several available options for managing emails in Sharepoint Portal Server or Windows Sharepoint Services. I've researched a couple and found some pro's and con's: