Here is a quick note on how to generate a proxy class for inclusion in your applications so you can consume and utilize the methods in a web service.
- Locate WSDL.exe (Typically in the Visual Studio Install Folder’s VC directory).
- Run the command wsdl.exe /out:<output file location> /l:<CS or VB) <web service location
- Example wsdl.ext /out:C:myProxyClass.cs /l:CS https://websericeurl.com/webservicename.asmx?WSDL
- In order to compile this into a dll just run the command csc /t:library /out:C:myProxyClass.dll C:MyProxyClass.cs
Take the resultant dll and include it in your projects to access the web methods of the target web service. If the structure (not implementation) of the web service changes you will need to generate a new proxy class to take advantage of the new web methods or continue using methods whose structure has changed.
I ran across a situation and thought I would post some of the time saving management possibilities of feature stapling in SharePoint 2007. The situation was a typical issue where there needs to be a lot of sites that have the same general features and layouts for default creation when auto provisioning the sites. In this situation there was a need to automatically provision a SharePoint site for every Account entity that existed in Microsoft CRM. Therefore, there would be a SharePoint document library, a default number of lists, some custom lists (stapled as features) and a custom homepage that displayed information. The solution to this is SharePoint Site Definitions (not to be confused with templates). By using a custom site definition these sites were able to be programatically created and updateable after the point of creation. The question came in though that certain sites would need additional items and those additional items would be an ever growing number of lists, calendars, custom web parts, etc… that may not apply to all sites in the definition but would apply to more than one. In comes features… Read more >>
Ran into this issue recently and thought I would post a solution to it. When attemption to reset IIS on a web server the following error can occur. The simple way to solve this is to run the command regsvr32 iisrstap.dll at the command prompt to re-register IIS.
Run IISRESET and you should be good to go!
If you are getting errors with your .Net applications due to application trust level while accessing a remote file share then the answer is simple. You can configure a custom code group to manage the trust level for that share within a given zone. Read more >>
I really like the “new familar” setup to MOSS 2010. Users whe are familiar with MOSS 2007 will see the typical installer and farm configuration wizard. Where it changes is when you first log into Central Administration. Microsoft has made the initial setup more streamlined to get the basic stuff that every install needs set up but also allows you to skip the setup wizard and dive right in. I like this for two reasons, the first being that there aren’t several pages to navigate to clear out the “farm configuration” alerts that are unnecessary to admins who have configured MOSS before. The second is that it doesn’t force you to go through the wizard. Allowing for both types of users to be satisfied.
One of the features I am most excited about diving into is the built in Business Intelligence components. Now that Performance Point Server 2010 is not a stand alone product but ”built-in” to MOSS Enterprise. It should bring a lot of visualization tools to the end user and help bring some great KPIs and Dashboarding tools without needing extra products.
Keep coming back as we dig further into the Business Intelligence features and the configuration side of MOSS 2010.
