I have recently started to look at EDI communications through BizTalk. Part of the EDI features in BizTalk is the use of BAM to track messaging. Amongst the applications we currently have built in BizTalk we do some SharePoint communication. This is also a possible component to our EDI solution. We also have plans to move to BizTalk 2010 in the near future, so today I started to build my new BizTalk Dev machine. I got a bit of a surprise when 2 parts of the required set had me setting a flag “Enable ......
Just a quick one to detail how this is done in case someone finds it useful. For those still getting into working with SharePoint features, a feature receiver is a class which contains some code you've written to execute when a feature gets activated. Or deactivated, installed or uninstalled. The key thing to note is that it's just standard ASP.Net debugging. The process is:- deploy the assembly to the runtime location, either the GAC or the site bin directory. Note that if it's the bin directory ......
The use of the OWSSVR.dll to filter data on the server side is a great idea as SharePoint can be slow and it tends to become the corporate dumping ground for all documents. Why delete it when we can retain it for auditing... So to be able to filter the data to the current entries before transmitting the data over the wire is great. It look like the perfect solution for my problem and it took a number of confussed hours before I found the posting by GaryJ @ Novotronix. I have copied it below. owssvr.dll ......
While trying to create a SharePoint 2007 web part I hit a problem that my web searches did not come up with any answers. The problem was I needed the web part that was imbedded in SharePoint to access the query string. I lucked out when examining the objects when debugging the code. The context object is available to the web part and it holds a pointer to the HttpRequests object which includes the Query string property.
I have recently been working on some web parts for a site hosted on a SharePoint 2007 (aka MOSS 2007). I was unable to get the custom properties to work. Paul Stork was kind enough to provide the answer. Apparently the method declaration changed between SharePoint 2003 and 2007. The reference that I had found was for the older version. Old Version (2003) private const string defaultText = "John"; private string text = defaultText; Browsable(true), Category("Test"), DefaultValue(defaultText), WebPartStorage(Storage.Shar... ......