CRM 4.0 Trial ready for download

Finally CRM 4.0 has been released to manufacturing (RTM) and trial versions can be downloaded here: http://www.microsoft.com/downloads/details.aspx?FamilyID=a9c110fd-aac8-4d2a-b401-7801b1866e82&DisplayLang=en

I would also like to point out that there are (at least) three different media types in general released from Microsoft.

MSDN - Can use MSDN or Trial keys.

Normal - Can use Trial or "Normal" license keys.

Volume Licence - Can only use volume license keys. If you want a trial, use it for a maximum of 90 days and uninstall it.

This is important when installing a trial environment that might be upgraded to production environment in the future at a customer. Consideration has to be taken to their current license agreement with Microsoft, and you can never use the MSDN media to install a production server.

There might be exceptions to this rule, for instance, a MSDN media might accept a normal license key, but I would not expect it.

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

Problems with ViewState in aspx page residing in Virtual Directory beneith MS CRM

I have been developing a front-end user GUI for a product configurator as a normal aspx-page. I started the development localy and then moved the project to our development server in a virtual directory bellow the CRM directory. (Please read earlier posts concerning problems with this and how to handle it) This is an unsupported way of placing your custom aspx-pages, but the disadvantages of doing it any other way are to great.

Well, my code used ViewState to store some data between requests and this had worked fine on my local machine. But, when I moved it to the virtual directory bellow the CRM site, the ViewState handling stopped. I tried to override the LoadViewState-method but it was never fired. I tried to explicitly set the page to have the property EnableViewState = true, but that didn't help either.

Then I remembered some things about how settings are inherited from the master website to all virtual directories bellow (i.e. the web.config settings are inherited). This is the reason for why you have to add some <remove assembly="...">tags to the virtual directory's web.config when deploying bellow the CRM website.

I thought that there might be some swith in the CRM web.config that disabled the ViewState and there was; the tag I found was the following:


<pages buffer="true" enablesessionstate="false" enableviewstate="false" validaterequest="false">

So, I copied the entire tag to the web.config in the virtual directory, changed enableviewstate="true" and magic, it worked!

So, specific advice: This is why viewstate might not be working in a Virtual Directory bellow the CRM site.
General advice: All settings in a websites web.config are automatically inherited to all virtual directories bellow. If you want to change anything, set this explictly in a local copy of web.config.

Over and out.

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

WebServiceStudio 2.0

SOAP is a great thing, not only does it get you clean, but it is also the foundation for most modern webservice communication. It is supposed to be platform independent.

A good thought but does, however, seem to have it's limitation. To be able to thoroughly understand the communication between the client and webservice a good program is needed that can help you study how the web service works and how the SOAP-messages are sent and received.

When working in a .NET environment, a .NET based client is very advantageous and a business partner of mine at the company Lemontree, Oskar Mattsson, suggested a very good application. I havn't had time to try it out fully yet, but it is also a GotDotNet-project so you can also read the code of how it is doing it's calls.

The name of the program is WebServiceStudio 2.0 and you can download it here:
here

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

Fake lookups = unsupported

My colleague Daniel Westerblom at WM-Data asked my a question concerning the fake lookups that I have referenced bellow and that I know are commonly used by many partners. The question was if these customizations are supported.

When I was at convergence I asked this explicit question to, I think it was, Clint Warriner (CRM Escalation Engineer at Microsoft Support) and he gave me confirmation on what I had suspected, that these customizations are not supported. They fall under the last point concerning unsupported customizations described in the SDK:
"The use of custom HttpModules to inject HTML/DHTML into the Microsoft CRM Forms."

Since the HTML DOM is modified, this is not supported.

The reason for this is most probably that Microsoft might choose to change this in future releases of CRM (for instance CRM 4.0) and might also have internal scripting references to objects they expect to be there according to the standard HTML DOM.

I don't know if these fake lookups will upgrade from CRM 3.0 to 4.0 without problems. If you have any experience of it, please let me know.

If you have any comments on this subject, please feel free to comment bellow. I always publish comments that concern the subject and are not directly offensive. (I have activeted moderation on comments just to avoid comment spamming).

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

Problems consuming webservices when developing locally

Usually I develop on a CRM server but sometimes, when a larger piece of CRM-independent part needs to be developed, I develop on my local machine.

Presently I am working in an integration project with an integration engine and needed to consume one of it's webservices. I did so and I added some code to handle it (intellisense working fine) but when I tried to run it, it crashed on the constructor or the service class with the following error:

System.IO.FileNotFoundException: File or assembly name gvy6umsk.dll, or one
of its dependencies, was not found.

There was also a reference to the Windows\Temp-directory. The filename is obviously some temporary filename for the proxy-object.

After checking the web a bit, I found the error to be caused by the fact that the user running the software, did not have read/write access to the c:\windows\temp directory. I fixed it and the program ran like it should!

So, if you are in the same situation, just fix the right for the windows\temp directory and you should be fine.

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

Great solution concerning javascript include files

Michael Höhne of Germany is a very resourceful CRM MVP and has just published a great posting on how to, in a simple and good manner create include files for javascript in a supported way. So, with great applause from me and hopefully the rest of the CRM community, give it up for Michael! Here is the link:

http://www.stunnware.com/crm2/topic.aspx?id=JS18

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

CRM License specification

I have previously blogged on the licensing issues of Microsoft CRM and I am still waiting for an answer from the Microsoft representatives in Sweden who have forwarded the question. As soon as I get an answer, I will let you know.

I have also been involved in some discussions concerning what the specifics of the external connection licese are. The following URL describes the details of this for CRM (and also other products). Please have a look:

http://www.microsoftvolumelicensing.com/userights/ProductPage.aspx?pid=161


Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

ASP page LifeCycle

Currently I am working with a product configurator via an integration hub, a very interesting project that is quite complex. One part of this is to create a dynamic apsx-page that let's the user choose properties of that are definied from the product configurator. Hence I am creating a new aspx-page that has to dynamically create lots of controls.

In order to do this properly, it is vital to understand the execution model of aspx-pages and the lifecycle of the page. I found this page that describes this, in an easy and understandable fashion. Please review it, if you are in similar needs as I.

http://www.15seconds.com/issue/020102.htm

Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

Nice video of Microsoft CRM use!

while checking out some CRM-blogs, I found this funny Microsoft CRM video.
Check it out!



Gustaf Westerlund
Microsoft Dynamics CRM Consultant

WM-Data/Logica CMG
www.logicacmg.com

Problems with Aug 07 VPC

Menno, the VPC god of Dynamics CRM land has created the very nice Aug 07 VPC of CRM 3. Sadly, a common error in it has to do with some new blocking of hacker attacks. It results in an error, that after a while of running it, you get a login-prompt and CRM stops working. The temporary solution is to restart IE.

Menno has written some about this on his blog, please read it. http://blogs.msdn.com/mscrmfreak/archive/2007/11/02/august-2007-vpc-fix.aspx

I personally liked "Method 1" described in the references KB-article. The details are described bellow. I have tested it for 5 minutes and it seems to be working. Here is a copy of the text:

Method 1: Disable the loopback check

Follow these steps:
1.
Click Start, click Run, type regedit, and then click OK.
2.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3.
Right-click Lsa, point to New, and then click DWORD Value.
4.
Type DisableLoopbackCheck, and then press ENTER.
5.
Right-click DisableLoopbackCheck, and then click Modify.
6.
In the Value data box, type 1, and then click OK.
7.
Quit Registry Editor, and then restart your computer.


Gustaf Westerlund
Microsoft Dynamics CRM Consultant

Logica CMG
www.logicacmg.com

Installed at Logica and a bit about CRM and Mobility

After some fiddeling, I am now more or less installed at Logica CMG. Some systems still need configuring and I still have to place a few calls to India (where our support is situated) to get it all up and running.

At Convergence, I had the opportunity to browse around and talk to some of the ISV (Independent Software Vendors) that supply 3:rd party addons for Microsoft CRM. One of the companies I found was CWR Mobility that have developed a very competent mobile client for Microsoft CRM 3 (and soon 4). It is a much more mature product (from what I could judge) than the normal Mobile Client, and it supports sometimes-connected scenarios and offline sync, as well as an offline SDK. So, if you are facing a customer with mobility demands, be sure to check out their products.

Gustaf Westerlund
CRM Consultant

Logica CMG
www.logicacmg.com

Today I attended the CRM 4.0 partner readiness tour and I took the opportunity to ask the technical specialist from Microsoft headquaters a lot of questions. In regard to my entry yesterday concerning licensing, we had an interesting discussion on how it can be managed and how it is handled in CRM 4.0.

In general the same licensing limitations apply as I described in my previous post. The new "light"-userlicense I described bellow will be a read-only user license with a reduced price. The external connector will also be available at a substanially lower cost.

However, we found some technical workarounds that the Microsoft representative actually said were ok but I havn't asked a Microsoft sales rep and I don't know if I should...

If you want to create dynamic reports based on CRM data, what you must do is to replicate all the data that you want to base your reports on to your own database. Then create all the reports based on this database, which can be called datawarehouse or something similar.

The same "intermediary" database can also be used when you have, for instance, an internal support page where you can submit your support issue, which is then added to the CRM as a Service case. Let the application write to a database and then create an service that periodically (like every minute or so) reads the new data, and writes to the CRM webservice. There are other similar ways of doing this (like sending emails from the form to a support que) and I think you get the general idea.

The legal workaround using a subsidary company with an external connector license is also valid, but will require you to buy the external connector which has a non trivial price.

I feel this is very strange, that you using a technical solution can bypass some licensing rules that actually should be changed.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Licensing of CRM and external software

During Convergence 2007 in Copenhagen, it got into a discussion with some Microsoft empolyees concerning the licensing issues when creating applications that directly or indirectly access CRM-based data.

According to what I have heard, it boils down to the fact that a user license is required for all users who interact with the data in any way. This means that no user license is required for a static report displayed in, for instance, SharePoint, but, as soon as there is any interactivity with the data, as for instance, drill down, a separate user license is needed.

So, if you want to display data in SharePoint that comes in whole, or part, from the CRM-database, make sure it is a static report, so that no special user license is required. Creating a report (with for instance SQL Reporting Services) that has drill-down, will require each user to have a user license.

This rises the question of what kind of licensing is needed to access OLAP cubes that are assembled from a data warehouse based on data from many different system, among these, Microsoft CRM. As far as I have understood a full user license is required for all users who can access the OLAP-cubes.

This issue will probably change in CRM 4.0 when there will be a new "light-user-license". Exactly what this means is still unclear and I have heard no details from Microsoft.

When creating any outside interaction with CRM, like a web based tool for submitting service cases, the separate "External Connector" license is needed. This is independant of the magnitude of the application or number of external users (company employees cannot use the external connector). It is also independant of if each user actually uses a named user or some common system user. I am unsure of the exact price for the external connector, but I believe it is somewhere around $40 000.

So, what does this mean for CRM-developers? That we have to have some basic understanding of the licensing modell and what limitations there are to it, so that our customers don't have to pay unnecessary license fees just because we thought that drill-down was a nifty feature in our report that is published on a SharePoint portal.

As many of you, I think these limitations are non benificial for Microsoft since they greatly restrict the possibilities of creating nice Mash-up applications and portals, something Microsoft technology is very good at and something I would view as a great advantage in comparison to Microsofts competitors.

I would also like to point out that I might be wrong in understanding some of these details, and I would be greatful if you could leave a comment if you know or think that I might have understood something wrong.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB / Soon Logica CMG/WM-Data
www.humandata.se

Common performance problem

Now Convergence is over and I feel stuffed with info and experiences. There is so much I would like to write about and so little time. I will try to spread it out a bit.

During one of the sessions Clint Warriner, an Escalation Engineer (he writes hotfixes) held a very interesting chalk-&-talk about CRM system maintanance and performance best practices.

It was crammed with goodies, and I will write more about it later, but one interesting thing he talked about was the possible delay in loading forms. He said this, most often, depends on the SQL server. When loading forms the list of which reports are relevant and so on, are also loaded from the Reporting server. This can, in some cases, take some time, and in some bad cases, really afect the load time of forms.

They have created a hotfix for this, that can be requested from Microsoft support (no cost) if you give the referece: KB 941592. It simply caches the information on what reports exist so that the request to the SQL-server doesn't have to be executed every time.

I will get back to the subject of performance tuning later.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Convergence EMEA 2007 in Copenhagen

I am writing this posting from my hotell room in Copenhagen on the end of the second of the three days of the Convergence event.

As you can expect, a lot of focus is on the new CRM 4.0 and all the brilliant new features of it. The other Dynamics products, mainly NAV and AX are also getting some of their well deserved air-time, but for me, it is all CRM! :)

So, anything interesting? Yes, a lot. I will be digging deeper into some of the topics later but would just like to write a little bit about everything I have seen and thought about thus far.

CRM 4.0 - What's new?
Well, a lot.

Multi, multi, multi!
Most of the focus is of course on Multilanguage, multicurrency and multitenancy. I personally feel that from the perspective of where I usually work, the two foremost "multis" are the most interesting. Multitennancy is maybe most interesting from a large enterprise view or hosting environment view

Internet facing
Microsoft Dynamics CRM 4.0 (as it formally is called, I will just call it CRM) has the ability to work as an Internet facing application, which CRM 3.0 wasn't (appart from CRM 3.0 SPE). This is really good news since it is really to be expected of the product. I havn't been able to get any info yet on how this works with MS ISA running reverse proxy (like you do in SharePoint) but I would imagine that it works (it didn't work very well in CRM 3.0).

Better Outlook client
The outlook client has gotten a major workover, and is now more stable and has a better interface. Some features to mention in that it will show a progressbar when loading and won't block the usage of Outlook during this time. It also allows for syncronization of other activity entities that just email, contacts, calendar and todo's, like for instance phonecalls and faxes. I havn't seen this in action yet.

Email
The email subject tokens are gone! Exaclty how it is handled in CRM 4.0, is still unclear for me, but it is probably handled in the mail header somehow. Emails can also be converted to leads and cases directly.

Autocomplete in lookup fields
One very timesaving feature is that the well know autocomplete/intellisense function has been enabled on all lookupfields, vastly reducing the clickyness of CRM. Good job!

Multi language
A lot can be written about this, but in general it uses one server installation language (default language) and then MUI-packs can be installed on either the server or the client to be able to run CRM in another language. Multi language is supported for picklists, sitemap, isv.config and more but not for CRM content. This might not seem like a problem but it is, since for instance products and subjects are CRM Content. If you are looking into using this feature you had better look into it thoroghly.

Multicurrency
The tenant is set up with one Base currency that will be used as such and will for instance be the currency used in reports. Pricelists are in several currencies and exchangerates can be set using the webservice.

Mail Merge
The mail merge has been improved a lot. Web client based mail merge has been activated (is only available using the Outlook client in CRM 3.0). Language specific mail merge templates can be created. Mail Merge has been enabled for custom entities.

CRM - Excel
Excel connections can be either iqv (like CRM 3.0) or ODBC. Refreshing of data is supported and a very very powerful feature of enabling updating back to CRM is also supported including creating new objects. This is very powerful since it can be used to clean data and do imports in a simple manner.

Office Communication integration
Office Communicatior has been integrated and you will get presence info in CRM. Very useful!

Resource Center
A new feature called the resource center has been added that allows role based info to be shown to the client. I don't know the specifics of what can and cannot be done yet.

New licensing
Two new licensing methods will be supported. Per device licensing and a "simple" user license, to be used for users who might only need to view CRM data shown in SharePoint in an agregated view. The details of the later licensing method, and what it will be called, is still very unclear. There will be no price difference between the per user and per device license. I will get back to you when I know more about this.

Diagnostics and troubleshooting
There are some additional tools to facilitate diagnostics and troubleshooting. Tools mentioned are Office Client Diagnostics and the possibility to switch on tracing in CRM (very performance demanding). There is also some sort of "self-healing" going on in the client. Exacly what it does is still unclear.

Entity relationships
This has been discussed before in this and other blogs. In short, all that you wanted from CRM 3.0 is there in CRM 4.0 - many - many, 1-1, self referential, system - system. I havn't heard of any limitations to this yet, but I am sure there are some (like maybe relationsships to "order product" or "quote product".

Workflow
The workflow handling is totally new and has been moved to Windows Workflow Foundation. (.NET 3.0). This is great news since this allows for REALLY advanced workflows.

In short, you don't have to go to the server to create simpler workflows, they can be created from the web gui. A lot more creation options are supported, publishing of workflows is supported, there is a nice wizard, you can create workflow templates.

Also, the "sales process" has been removed and "stages" has been added to normal workflows, and can hence be used in all workflows, for all entities.

Workflows can now traverse relationships, the date-time handling is a lot better and the branching options has been improved a lot with support of "else" and "wait" statements. Dynamic data in forms is also supported using Workflow.

Reporting
This is also an area that has been re-written a lot. Reports are now run directly on the CRM server, which gets rid of all Kerberos delegation issues. There is a nice end-user report wizard that is about as hard as creating an advanced find saved view. Reports are language specific (if you want them to be). There is support for scheduling directly from CRM. There is support for offline reports.

Importing
There is now a nice wizard for importing data and it is possible to save and export the datamapping. It supports all entities. It supports backing out of an import, even several weeks later.

Duplicate detection
An advanced and customizable dupicate detection exists that allows for cleaner data.

Uppgrading
As promised, all supported customizations are supported for uppgrading, including callouts. There is a nice wizard that checks for possible problems before. Even though there are nice promises, I would really like to see this work before I believe it! It is almost to good to be true!

Exporting
The exporting of security roles is now supported. When exporting all customizations, even all dlls that have been added as plug-ins are included. This will enable the movement of an entire solution from one server to another. (Ex. test to production).

Scale out possibilities
CRM has been split up into several services that can be distributed to several machines, so workflow, for instance can be moved from the front-end web servers to dedicated servers allowing for better scale-out options and greater performance.

RW-Metadata
The metadata webservice now enables writing, so new attributes, entites etc. can now be created programatically!

Create users in bulk
This has also been discussed in other blogs, but in short, it allows for the bulk creation of many users at once.

Well, that was a short overview of some of the new features in CRM 4.0 and I have hardly mentioned plug-ins.

I have attended lots of different sessions and will write a lot about it soon! As for now, the dinner table is calling (as is my belly!).

Over and out!

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB (soon WM-Data)
www.humandata.se

Microsoft Virtual Earth Demo

Integrating with map services like Microsoft Virtual Earth, Google Maps can bring your CRM or SharePoint application great increases in features at a relativly low cost. Microsoft uses Microsoft Virtual Earth internally and the Microsoft SharePoint Products and Technologies Team Blog has written an interesting posting about this which includes a reference to a codeplex project including all code for the internal project.

I havn't checked it out, and it is used for SharePoint in the example but I believe that a lot of the code probably can be used to develop a Virtual Earth driven map service in Microsoft CRM.

So, without further ado, please read the posting and check out the codeplex project if you are interested!

http://blogs.msdn.com/sharepoint/archive/2007/10/14/announcing-community-kit-for-sharepoint-virtual-earth-maps-on-sharepoint.aspx

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Mr Dave writes some about Plug-In development

Mr Dave has written an interesting blog in plug-in development, which is the replacement for the callout-techniques used in CRM 3. There are a lot of architectural differences between callous and plug-ins. If you are planning to use plugs, dig in:

http://crm.davidyack.com/journal/2007/10/14/using-prepost-images-in-plug-ins.html

I hope to be writing some postings of my own concerning CRM 4.0 soon, but I still havn't got my hands on a version :(

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Stunnware on CRM 4 development

Michael Höhne who runs the site Stunnware has written an interesting blog posting on how development differes between CRM 3 and CRM 4. It is very interesting and very usefull. If you plan to develop using CRM 4, I highly recommend that you read it.

http://www.stunnware.com/crm2/topic.aspx?id=CRM4MultiTenancy

Next week is Convergence EMEA in Copenhagen. If you are planning to go there and would like to meet, please drop me a line and we can arrange it.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

CRM 4 VPC available on partner source

Ben Riga has made a CRM 4 VPC available on partner source. In other words, you have to be a Microsoft Dynamics Partner to be able to download it. Unfortunatley, I am not, yet, so I havn't had the possibility to download it. When I start at WM-Data/Logica CMG, I will be however, and look forward to checking it out!

Here is the link if you have access: http://blogs.msdn.com/benriga/archive/2007/10/08/titan-now-available-to-all-dynamics-partners.aspx

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

crm 4, Crm 4, CRM 4, CRM 4!!!!

Very exciting times...
Lots of CRM 4 related information all around. Microsoft UK CRM Blog has some interesting information:
http://blogs.msdn.com/ukcrm/

And if you havn't been there already, keep a steady eye on The CRM Teams blog:
http://blogs.msdn.com/crm
They have added some links to videos of CRM 4.

Here is also an interesting blog containing info about CRM 4. It details a bit more the Import/Migration tool included in CRM 4.

I still have some unanswered questions:
1. Is there support for global javascript includes (like globalcustom.js)?
2. Is there a VPC out yet?
3. Other javascript support?

I would also like to look deeper into the offline API that is included.

And callouts have been renamed to plug-ins, and are "Tennant"-specific, meaning that they can be assigned to only one of the installed companies on the CRM server. Very nice indeed!

When I know more, I'll get back to you!

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

I'm moving on!

November the 9:th will be my last day at Humandata here in Sweden. My new employment will be at WM-Data/Logica CMG where I will be working as a consultant with special focus on Microsoft Dynamics CRM development.

This means that I will focus even more on MS CRM and less on SharePoint. Don't get me wrong, I really like SharePoint and will probably use it for integration purposes with Microsoft CRM many times. This new employment will give me the opportunity to work with some of the largest MS CRM implementations and I will also be assisting in building a team of (hopefully) excellent MS CRM developers and consultants. If you feel that is you, please let me know, and we'll meet and discuss it. It will also be very interesting and instructive to work with the very experienced CRM professionals at WM-Data.

I will still be activly blogging to get you the latest and most useful tips, but I will focus more on Microsoft CRM, even though an occational SharePoint posting might occur.

I would also like to say that I feel very sad to leave the company Humandata which is a great place to work and it has been a privilage to work with some of the most competent people in the business. If you are a skilled SharePoint consultant (or want to be), please contact Göran Husman (SharePoint MVP and owner of Humandata), I promise you wont regret it!

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Problems with Peoplesearch in MOSS 2007

Today I ran into some problems concerning People-search in MOSS 2007. My customer was using https for their main sharepoint site and I had installed the mysite host on the same web application (in https://servername/mysite) according to the specifications found around the net.

Well, my customer just couldn't get the people search to work, and I had heard that there were some problems with using it on a site that runs on https (http with ssl), so I wasn't very surprised. As a bit of backgroud, the peoplesearch is set up as a contentsource in the search using sps3://servername. The server in this case should be the web application hosting mysite.

Well, how to solve it. First of all I tried to just create and extension of the sharepoint application on http port 2000 (http://servername:2000). It worked just as it should, when I browsed it, it worked and I was also tranfered to the default site (https://servername).

I tried adding this as a content source instead of the old one, in other words:
sps3://servername:2000, sadly it didn't work.

As a matter of fact, we had got it to work previously in the same environment. We had first installed sharepoint on http://home and then added https://home.company.com with an extension and an alternate access mapping. The later was used as the address to be used from the outside, by using MS ISA as a reverse proxy. After a while, the customer complained about problems with people copying/emailing url:s that didn't work from the outside. (the url was http://home/... and not https://home.company.com/..., so not very strange. This resulted in the action of removing the alternate access mapping of http://home (the original one) so that only https://home.company.com remained (and was hence set at the default). This worked great, people could enter "home" in their IE and they would reach the site https://home.company.com.

However, when I removed the alternate access mapping for http://home, people search started failing.

So, the remedy, I added an alternate access mapping for http://home:2000 in the zone Intranet (doesn't really matter, which zone as long as it isn't the default), re-indexed the search server and made a full crawl that worked like a charm! The point of using TCP port 2000 was that is is very unlikely that a user might just happen to enter that, it could just have been 1234 aswell...

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

First Titan/CRM 4 screenshots!

If you, like me, havn't been able to test or have a look at the new Microsoft Dynamics CRM 4 (code named Titan), you can now. I havn't seen any VPC out yet public but will let you know as soon as I know.

In the meantime, have a look at Stunnwares/Michael Höhnes site where he writes about the many new features of CRM 4. It's been a long wait, but it has been worth it! CRM 4 seems to be great!

http://www.stunnware.com/crm2/topic.aspx?id=TitanBeta3

Gustaf

MS CRM 3 and Exchange 2007

As many of you probably have customers running Exchange 2007 or are considering running Exchange 2007, careful consideration has to be taken to the fact that the current CRM Email router does not support Exchange 2007 due to the fact that it is a 64 bit program, and the router is not. This is going to be fixed in CRM 4. For more information have a look at the CRM Team Blog: http://blogs.msdn.com/crm/archive/2007/09/27/crm-3-0-and-exchange-2007-compatibility.aspx

Gustaf

Interesting feature in SharePoint webpart properties

I am currently developing a customized search webpart for a customer and I wanted to move all environment specific variables to the webpart public properties so that they can easily be changed and the same dll can be used in all environments (dev and production). One of the properties was Scope, which defined search scope to use. It was defined in the following way:

private string scope;

[Browsable(true), Category("Settings"),

DefaultValue("Documents"),

WebPartStorage(Storage.Shared),

FriendlyName("Scope"),

Description("Define Scope of search"),

XmlElement(ElementName = "Scope")]

public string Scope

{

get

{

return scope;

}

 

set

{

scope = value;

}

}

 

Well, just to be on the safe side, I set the web part property to "Documents", which is also what I had used as default. I was very confused the next time I opened the "Modify Shared Webpart" menu and found that the field was blank! First I thought there was some error in how the property was defined, but after a while I found that it actually blank the field if it is set to the value defined as default (in this case "Documents").

So, if you run into this little "feature", don't be afraid, everything is just as it should be!

Gustaf

Creating custom views for MS CRM 3

Any modification made to the main or META-database is considered unsupported customization. Not very strange, since you never know what new fields or tables Microsoft might add to the database.

Sometimes, however, especially when working with reports, it can be useful to create your own views that aggregate data to your needs. Adding a view to the CRM database might be the easiest and you will probably be ok as long as you are a bit careful when naming the view. However, you don't have to do it this way. You can also create a new database on the same server and create your view in this database. To be able to access the views (and if you still want to play unsupported, tables), just add the database name in front of the viewname. For instance:

SELECT * FROM MyCompany_MSCRM.dbo.SystemUser;

The "dbo" part doesn't have to be there but is added by the view creator GUI, so I left it there to avoid any misunderstandings.

Unfortunately, the "Add Table" function in the GUI doesn't support selecting views from other tables even though it is supported in the database.

As far as I know, it is also possible to connect to a view in a database on another server. I don't know how this is done and don't really see the relevance from a MS CRM 3 perspective, but if I find out how, I will let you know.

Gustaf

Silverlight and Dynamics CRM

Silverlight is a new product from Microsoft that can be viewed as the same sort of plug-in as for instance Flash, Java Applets or ActiveX. There are two feautres that make it stand out from the rest, namely:
- Vector based graphics built on the new Windows Presentation Foundation (a part of .NET 3.0). The definition of the GUI is definied in a langauge called XAML.
- From Silverlight version 1.1, you can write managed code. In other word you can finally start working with C# or VB.NET on the client side instead of the irritating language javascript.

These two features make the foundation for a more user friendly and more rich experience of using the web, something at least I have been longing for. Being able to use managed code/CLR-code, will make web development a lot easier and speed up the process of making more robust and reusable programs.

On the CRM Team Blog you can download an example of how silverlight can be used in conjunction with Dynamics CRM 3. I saw that some people had had some problems with it, and I havn't had time to test it myself yet, so be advised.

Here is the link: http://blogs.msdn.com/crm/archive/2007/06/19/crm-and-silverlight-integration.aspx


Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Office 2007 + CRM = true

Michael Höhne is one of the most generous and knowledgable people in the Microsoft CRM 3 community. His webpage http://www.stunnware.com/crm2/ hosts lots of very interesting articles, both for advanced Microsoft CRM developers and more novice Microsoft CRM application professionals. For instance, he has a very interesting posting showing an example of how to use the new file format OpenXML that comes with Office 2007 in conjuction with Microsoft CRM 3 to make very powerful software with almost no effort (ok, a little effort :)

Have a look: http://www.stunnware.com/crm2/topic.aspx?id=OpenXml

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Request hotfixes online

The most common way of requesting a specific hotfix for Microsoft Dynamics CRM or SharePoint is to call Microsoft Support (they cannot be downloaded directly). However, there is also a webpage where you can request a hotfix online. Have a look an add it to you favorites, you will probably need it.

https://support.microsoft.com/contactus2/emailcontact.aspx?scid=sw;en;1410&WS=hotfix

Gustaf Westerlund
Microsof CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Fake lookups

As I mentioned before, when I was working with the company Cybernetics, there is a way of creating false lookups when it might not be possible to do so normally (for instance system-system relationsships).

The blog http://andrewn23.blogspot.com/ describes in detail how this is done, so, if you are interested, please have a look. This technique can of course be enhanced in many ways.

Also, I am not certain if this technique is supported since Microsoft might decide to change the way some of these more internal pages (lookupsingle.aspx) work, hence breaking the customization.

The blog also mentions some hazards of using allcolumns that are very worthwhile reading (I like to use them to increase development time and change to specific attributes when I get performance issues).

So, take some time and have a look at it, I am however sad to see that the last entry was in october 2006.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Selecting multiple records from a grid in MS CRM 3

Using isv.config customizations you can add buttons to the menybar above a grid (next to "More Actions"). A special technique has to be used to fetch the selected records and Ronald Lemmen wrote some about it this summer, here: http://ronaldlemmen.blogspot.com/2007/06/fetching-selected-records-in-grid.html . I had reason to try it and ran into problems when the url of the file containing the javascript was on a different server (different tcp-port has the same characteristics as a different server from an IE viewpoint). The window.dialogArguments was null. I tried to modify the settings in IE but found no way of getting around the problem except for setting up a virtual directory bellow the CRM-site containing the html-file.

So, if you run into similar problems, try moving the html-file to a directory on the same server (from an IE standpoint).

Gustaf

User based Timezones in SharePoint 3

I have been on the look for this feature for some time. I've heard it's there but never found it. Now my colleague Sebastian Tegel found it. Have a look if you're interested!

http://sebastiant.blog.com/2079971/

Gustaf

Environment independent solutions

Developing CRM solutions that are environment independent is not trivial. By just adding a webservice you are making your code dependant on the CRM customization of that system. If you move the solution/dll:s to another system you will be running a risk of your code not working. This is especially problematic for ISVs since they never know what system their product will be installed on. However, there is a good way to handle it. The best way is to first use a plain out-of-the-box CRM system and use the program

C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin\wsdl /out:c:\temp\myCRMProxyClass.cs http://localhost:5555/mscrmservices/2006/crmservice.asmx?wsdl

This will create a file called myCRMProxyClass.cs is c:\temp.

Add this to your project. This is in essence the same this as adding a web reference and adding "using CRMSDK" or whatever you named it. Hence you can access all the CRM webservice classes.

Then create the service-instance and set the url by using the registry-key added during the installation of Microsoft CRM. Have a look here if you want to know how. http://ronaldlemmen.blogspot.com/2007/08/creating-environment-independent.html

If you have other environment specific data, it should be placed in the web.config / appsettings (if using a normal web-site/virtual directory) or you can use the AssemblySettings.dll (has to be downloaded, not from Microsoft) to create a assembly specific config-file, alternatively, add you own keys to the registry.

I hope I have given you a few hints on how this is done. Happy coding!

Gustaf

Activate a Workflow using Javascript

Workflows are a great tool. They are quite simple to create, even non-programmers can actually create them and they are flexible. However, there are some problems with workflows in CRM 3 (how workflows are handled in Titan/CRM 4 will be interesting to see) for instance, a workflow cannot be activated when an entity is updated, only when it is created, when it changes status, when it changes owner and of course, manually.

Mitch Milam has written an interesting post on his blog concerning how to activate a workflow using javascript. You can read about it here: http://blogs.infinite-x.net/2007/06/15/launching-a-workflow-rule-from-javascript/.

A bit of caution is however advised. I would actually prefer to have the workflow being activated by a PostUpdate-callout instead, to make sure that it is only run once. Activating a workflow on the on-change event can be a bit hazardous since it is very possible that the event is triggered several times on the same form before it has been saved.

Never the less, it is a good posting and can probably give you an idea or two about how to programmatically activate CRM workflows. If I wasn't block from using my own virtual directory or website with my own aspx-files, I would also prefer to trigger the workflow from an aspx-page and call the aspx-page using AJAX. Have a look at the class ExecuteWFProcessRequest in the CRMSDK as it enables you to execute a workflow using the web service.

Gustaf

SQL COALESCE

SQL Reporting Services is a great tool. It allows you to create flexible and exportable (to pdf etc) reports. However, things sometimes get a bit complicated and a normal problem that you face is the problem of columns containing null-values that you want to use for calculations. For this there is a nice function called COALESCE which replaces null with the value directed.

For example:

SELECT firstname, lastname, age FROM contacts;

Might return the list:

firstname        lastname        age

John            Smith            5

Peter            Jacks            null

If you want to use the age-column to do some calculations or you just don't want it to be null, just change your SELECT-statement to:

SELECT firstname, lastname, COALESCE(age, 0) As NewAge, COALESCE(age, 0) * 2 As DoubleAge FROM contacts;

This will give you the result:

firstname        lastname        NewAge    DoubleAge

John            Smith            5        10    

Peter            Jacks            0        0

 

A useful and simple functions, to get you out of some nasty trouble when doing for instance LEFT OUTER JOIN, RIGHT OUTER JOIN or FULL OUTER JOIN when the risk of returning null is great.

Gustaf

Humandata AB

Javascript – define functions and programmatically attach events

Since we're on the subject of javascript I might as well add some more stuff. First of all, how to define you own functions, then how to programmatically bind a function to an event, for instance, onchange of a field.

This mainly concerns Microsoft CRM but the technique can also be used in SharePoint, although javascripts aren't as common.

First off, how to define a function.

There are actually several different ways, for instance the normal:

function myfunc1(param1, param2)

{

alert("myfunc1");

}

 

And the one with a weird sort of syntax:

var myfunc2 = function(param1, param2)

{

alert("myfunc2");

}

 

In CRM 3, these can actually be defined within the onLoad, hence creating some ways of code reuse. These functions will be available for all event in the page since they have been declared in the onload.

This leads me to another point, that a function has to be defined before it can be used. Hence, in the example above, myfunc2 can call myfunc1, but not the other way around. If you try, you will get strange error messages saying stuff like "null is not 'null'".

Secondly, you can bind events to functions using code. There are several ways of doing this as well (what did you think!?) and they mainly differ based on which browser you are using. If you want to read some more on the subject, if you want some more info on event binding in javascript, please have a look at this very instructive page: http://developer.apple.com/internet/webcontent/eventmodels.html

First the simple method by just setting the onchange attribute.

crmForm.all.ext_myfield.onchange = myfunc2;

 

or

document.getElementById("objectid").onchange = myfunc2;

 

This has the advantage of a quite simple syntax and, if you want it, the override of previous events.

The second way of doing this is using the attachEvent method. As far as I've read, there are some differences with syntax between browsers, but since neither MS CRM nor SharePoint work in any acceptable way in anything but IE, this is not a big issue. Here is some example syntax:

crmForm.all.ext_myfield.attachEvent("onchange", myfunc2);

or

document.getElementById("objectid").attachEvent("onchange", myfunc2);

 

The main advantage of this method is that you can attach several functions to one event, hence, not overriding other handling.

Bellow is an example html-file which demonstrates this:

<html
xmlns="http://www.w3.org/1999/xhtml">

<head>

<script
type="text/javascript">

var myfunc1 = function()

{

alert("myfunc1");

}

var myfunc2 = function()

{

alert("myfunc2");

}

var loading = function()

{

alert("running");

document.getElementById("btTest").attachEvent("onclick", myfunc1);

document.getElementById("btTest").attachEvent("onclick", myfunc2);

}

</script>

</head>

<body
onload="loading();">

<button
id="btTest">Click me</button>

</body>

</html>

If you copy this to a file called test.htm and test it, you will see that when clicking the button, myfunc2 will be executed first and then myfunc1.

So, all put together, this can be used to a great extent in MS CRM 3, where you can now put all code in one place, the onLoad script, define some functions and then bind the onchange event of all the attributes you like in the same code. Remember to define the functions before you attach the events.

I havn't seen CRM 4 / Titan yet, and I don't know what features it will have in this aspect, but if it includes the feature to be able to add a global javascript file that will be included on all pages, this would be very very useful when using techniques like this.

And remember, javascript is an ugly beast, but it is very useful! J

Gustaf Westerlund

Humandata AB

Window.close() in javascript acts a bit strange…

Javascript is a strange language, it is often confused to be Java, which is very far from right, and the syntax can often be thought to be as consistent as C# or Java. Not the case. Javascript is a strange and weird beast, that when tamed can be a very strong ally. Taming it can however really get on your nerves!

There is one method working on the object window, called close(). Hence it is called using window.close(). It does the simple thing of closing the current browser window. No more, no less.

Well, actually, it does it in a strange way. Have a look at the following code that is executed in body onload. What is going to happen?

Alert("Start");

Windows.close();

Alert("End");

 

I will give you two options:

Option 1:

1. A dialog window showing "Start" will show.
   
2. The current browser window will close.
   

Option 2:

1. A dialog window showing "Start" will show.
   
2. A dialog window showing "End" will show.
   
3. The current browser window will close.
   

Well?

You would think that option 1 is correct, well, it isn't, the script is executed according to option 2. For some reason, window.close() doesn't actually close the window, it signals it to close and when the onload has reached its end, it is closed. I havn't checked to see if this behavior only happens when executed in onload or if it is the same all over. Be aware though, it might not work as you'd expect!

Gustaf

How to add a virtual directory below your SharePoint or CRM website

Sometimes you would like to create a virtual directory bellow for instance the SharePoint main site. Lets say you MOSS is installed at http://intranet and you would like to create your own virtual directory with your custom made aspx-pages at for instance http://intranet/custom. Well, if you use the IIS Management Console, add a virtual directory to the website, and add an aspx-page to that virtual directory, you will get errors saying that the application cannot find certain assemblies. This is due to the fact that these assemblies have been referenced in web.config using <add assembly="name-of-assembly" / > tags. Due to the way IIS works, these references are automatically inherited to all sub-directories, in this case, you virtual directory.
So, what to do? The simplest way to handle this is to add <remove assembly="name-of-assembly" / > tags to the web.config that resides in your virtual directory. This will explicitly remove the reference created by the parent website. Remove them one by one and soon you will be able to run your code just as you would like.
One good advantage of using adding your code to a virtual directory bellow the main site instead of using a new website at for instance another host header or TCP port, is that you can address your code using server relative urls. In essence, if you created an aspx-page at http://intranet/custom/mycustompage.aspx. If you address this page from the SharePoint, you can use the url: /custom/mycustompage.aspx without http:// or the servername. This also gives you the benefit that the page is on the same server, hence no security problems with IE.
In SharePoint, make sure that the address of your virtual directory is NOT bellow any wildcard included och explicitly included sites (in the setup of the webapplication in central admin).
Please note that adding virtual directories bellow the CRM root is an unsupported customization. This is due to the fact that Microsoft might release an update that adds a directory with the exact name of you virtual directory. This would give rise to either the fact that your code stops working or more likely that the content of the directory added by Microsoft cannot be accessed.
Gustaf Westerlund
Humandata AB

Showing SQL Reporting Services reports in Microsoft Office SharePoint Server 2007-08-31

Today I was working with a customer who wanted to show their SSRS 2005 reports in SharePoint. As many of you might be aware, from SP 2 of SQL 2005 there is an option of storing you reports on the SharePoint Server. Very nice, but I havn't really tried getting that to work with MS CRM 3, so the SSRS I was using ran in normal mode, i.e. not SharePoint integration. However, I did want to show the reports and the reports explorer in SharePoint. For SharePoint v2 there has long existed RSWebparts.cab, which is a web part package consisting of two web parts; report viewer and report explorer.

After a bit of looking I couldn't find it for SharePoint v3, and found some information saying that the old webparts actually still worked well. So, after the always so tedious work of trying to locate the file, RSWebparts.cab (it cannot be downloaded from the Internet as far as I know) I installed it using stsadm –o installwp -o addwppack -force –filename "C:\temp\RSWebParts.cab" –globalinstall (use stsadm –help addwppack to see possible syntax), and adding the RSWebparts.dll as a safecontroll (with the correct strong name). I got it to work, just as nicely as it did in SharePoint v2. So, my suggestion to you, if you have the same need, use the old one.

And where can you find the file? It is installed in some impossible path bellow c:\program files\SQL Server of a SQL 2000 SP2 (or greater) server. So, get your hands on it, and don't let go. I don't think I can publish it here though, due to copyright reasons.

Gustaf

Entity and attribute information

I was reading a bit on the CRM Teams blog and read a posting on the fact that there is an aspx-page that lists all entities that can also show all attributes of the entity. Read the post here or just brows to: http://<yourservername>/sdk/list.aspx.

You learn something new, every day J.

Gustaf Westerlund

Humandata AB

How to stop infinite recursions/loops in PostUpdate Callouts

As many of you who work with development in Microsoft CRM know, callouts is a great tool. Lots of different tasks can be left to be handled by callouts and they are even run when offline data is resynced to the main system. However, a common problem when working with PostUpdate callouts is that the code wants to update the object that created the callout, hence executing the calloutcode again, which might result in an endless recursion.

I recently ran into this problem working at a customer of mine, and found a nice generic way of solving it using the thought behind the design pattern object factory or single instance.

I guess you want some code! Well, the basis of this solution is to have a static instance of a collection that keeps track of if a certain key just has been run. I use the collection StringCollection. It is simple, and just what I needed in this case:

private
static System.Collections.Specialized.StringCollection justtreated;

 

Then I created a method that is supposed to return false the first, third, fifth… time it is called and true every second, fourth, sixth… time it is called with a certain key.

 

private
bool JustDone(string key)

{

    if (justtreated == null)

    {

        justtreated = new System.Collections.Specialized.StringCollection();

    }

    if (justtreated.Contains(key))

    {

        justtreated.Remove(key);

        return
true;

    }

    justtreated.Add(key);

    return
false;

    }

}

The method is not very complicated. First off, it makes sure that the static variable has been created. Then it checks if it can find the key string in the string collection. If it can it will remove it and then return true. If it cannot find the key, it will add it to the collection and return false.

Since, this method is working with a static variable that will remain in memory between instantiations of the class, hence the data will remain between PostUpdate calls.

Then in the beginning of the PostUpdate method just call JustDone() with the object key (or some other unique key) and if it is true, just "return".

Gustaf Westerlund

Humandata AB

August 2007 MS CRM VPC is here!

I've been bad at reading all blogs recently. Full of work and my private time is now mostly filled with my daughter Nora, hence less time to read up on blogs.

We have all (?!) been waiting for the new MS CRM VPC and it has now been released. It can be downloaded from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=57394bc8-5ecc-422e-a066-34189f48f8c8&displaylang=en

I havn't downloaded it myself yet, but I will soon.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Java, javascript, jscript and so forth

When developing software customizations for SharePoint and MS CRM 3, javascript is often used. It can easily be confused with the totaly unrelated language java. Mennotk's blog has a posting linking to another blog that describes in a bit more detail what javascript, jscript and so forth really is. Being a developer in MS CRM and SharePoint, where this is one of my main tools, I found this quite enlightening and it sheds some light on some question marks I personally had on the subject of javascript and client side scripting.

Please have a look if you are interested: http://blogs.msdn.com/gauravseth/archive/2007/08/15/the-world-of-jscript-javascript-ecmascript.aspx

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Javascript event handling and dynamic lists in SharePoint

As many of you already know and probably have used, it is possible using javascript to create dynamic drop-down-lists. For instance one drop-down list that selects country and another that lets you select a city in that country. Depending on which country you select, you want the options in the city drop-down to change.

This is a quite common task in MS CRM where javascript is a common tool. In SharePoint however, javascript isn't as common. I am currently working with a colleague of mine, Sebastian Tegel, at a large swedish customer of ours. They had this requirement on some metadata in a SharePoint library so Sebastian and I used the same principles as I usually use in MS CRM to create dynamic drop-down lists in SharePoint. Sebastian has a very nice and instructive posting on his blog on how this is done. Please have a look at it: http://sebastiant.blog.com/2023682/

In the posting before that, he also describes how to create your own custom edit form for a document properties page. This is very useful in these cases, so please have a look at that as well. (http://sebastiant.blog.com//custom+forms/).

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Not so simple SharePoint and CRM integration

A customer of mine wanted to integrate their MOSS Ent with CRM 3. Specifically they wanted to be able to handle documents in CRM with SharePoint, not surprising since the document handling in MS CRM 3 is bad, if you are a bit positive. They were running 2 servers, one with CRM and one with MOSS Ent. Both with their own SQL 2005 installations (to avoid problems with SPN:s and such).

The solution? I based the solution on my previous posting from October 2006 where I described how to do this; Simple SharePoint and CRM integration (http://gustafwesterlund.blogspot.com/2006/10/simple-crm-and-sharepoint-integration.html). That was WSS 2 and both applications were running on the same server. So, not really the same setup, but, I felt, it shouldn't be a problem.

My plan was to create a SharePoint site using a specific custom template on the Account PostCreate callout. The callout would set the websiteurl attribute and an onLoad javascript would show a custom aspx-page that shows a documents webpart using the minimal.master (in order to hide all the SharePoint specific framing).

I started off by creating the PostCreate callout. Not a problem, just create a normal class file with the following content:

using System;

using Microsoft.Crm.Callout;

using Callouts.CRMSDK;

 

namespace Callouts

{

           ///
<summary>

           /// Summary description for Class1.

           ///
</summary>

           public
class Account: CrmCalloutBase       

           {

                      public Account()

                      {

                      }

                      public
override
void PostCreate(CalloutUserContext userContext, CalloutEntityContext entityContext, string postImageEntityXml)

                      {

                     
 

                                 CrmService service = new CrmService();

                                 service.Credentials = System.Net.CredentialCache.DefaultCredentials;

 

                                 service.CallerIdValue = new CallerId();

                                 service.CallerIdValue.CallerGuid = userContext.UserId;

 

                                 systemuser user = (systemuser)service.Retrieve(EntityName.systemuser.ToString(), userContext.UserId, new AllColumns());

                                 account acc = (account)service.Retrieve(EntityName.account.ToString(), entityContext.InstanceId, new AllColumns());       

 

// Code to create sharepoint site/subweb and set acc.websiteurl to the url.

                                 service.Update(acc);

 

                      }

 

           }

}

 

And add a web reference to the CRM webservice (look in the SDK to find the exact URL). As you probably can see, I called it CRMSDK (strange name actually, but it´s tradition).

And the callout.config.xml looked like this:

<callout.config
version="3.0"
xmlns="http://schemas.microsoft.com/crm/2006/callout/">

           <callout
entity="account"
event="PostCreate">

                      <subscription
assembly="Callouts.dll"
class="Callouts.Account" />

           </callout>

</callout.config>

 

Well, I modified the code and set some attribute of the account to something just to make sure it worked. It did.

How to create a site in SharePoint from one server? Well, first I tried adding Microsoft.SharePoint.dll which contains lots of nice stuff to access the SharePoint data. This was the technique I had used previously and thought it might be good this time too. But no, it can actually only be used on the same server as SharePoint and not on some other server.

There are still a lot of nice web services in SharePoint, I could probably find some web method that would let me create my site. I started by looking in the WssSDK…

But I could find anything useful. The natural webservice would of course be webs.asmx and it contains lot of nice functions to handle SharePoint webs, like GetWeb() and so on. But I found no way of creating a new site. In the admin.asmx I found a method called createSite() but that creates sitecollections which is not really what I wanted. (Each sitecollection has unique security handling, template and sitedefinition setup and a lot of other specific stuff) My customer has around 5000 customer and I would want to create 5000 sitecollections.

I started searching the Internet. But, no. All I could find was a blog entry by Nick Swan describing how to use admin.createSite() (http://weblog.vb-tech.com/nick/archive/2006/03/07/1472.aspx).

I contacted Pontus Haglund and Kalle Becker at Microsoft and my colleague Sebastian Tegel and asked them if they knew how to do this or could assist in any way. They didn't unfortunately.  

I was left with only one major option as I saw it; creating my own web service that used Microsoft.SharePoint.dll functions to create the web site (subweb). I had found a blog that described how to do this (http://blogs.ittoolbox.com/km/sharepoint/archives/creating-a-custom-web-service-for-sharepoint-13553). So, I thought that it shouldn't be that big of a hazel. To make sure my SharePointcode worked, I first created a normal windows forms application that created a site according to certain variables. I found that the following code worked very well:

 

string url = "";

SPSecurity.RunWithElevatedPrivileges(delegate()

{

SPSite siteCollection = new SPSite("http://intranet");

SPWebCollection subSites = siteCollection.AllWebs["customersites"].Webs;

 

SPWebTemplateCollection templates = siteCollection.GetCustomWebTemplates(1033);

SPWebTemplate template = templates[0];

 

SPWeb mySite = subSites.Add(name, Title, Description, 1033, template, false, false);

mySite.Update();

url = mySite.Url;

});

return url;

 

After a suggestion from my colleague Sebastian Tegel, I ran all the code with Elevated Privileges. Not sure it is actually needed but I added it to make sure that there isn't any security issues with the current user and permissions to create sites.

Now, I just had to follow the blog I had found. Again my misfortune struck me, as I was unable to make any sense of it. I got the web service to work as long as I didn't use any SharePoint functions. When I did, I got the following error:

System.IO.FileNotFoundException: The Web application at http://intranet could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

   at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)

.

.

.

 

I was using the exact same code as I had tested in the forms test application so there wasn't any problems there.

The blog post mentions a lot about strong naming assemblies but it doesn't reference it with the strong name and my experience told me that this error probably was due to Code Access Security (CAS) problems. The assembly should be strong-named, placed in the GAC and referenced using the strong name.

I think some important pictures has fallen out of the blog why it doesn't make much sense. It did however mention that there was a walk-through on msdn that described the same thing. This was my next lead on the way to my goal of SharePoint document handling In MS CRM 3.

I found the walk-through (http://msdn2.microsoft.com/en-us/library/ms464040.aspx) and followed it minutely. It gave me a lot better feeling than the first blog posting I had found. In short, it described how to create a web service asmx-file that references a strong named assembly with a class of web methods in it. When created, the program disco.exe was used to create wsdl and disco files for the web service. When these had been created, the were renamed to become aspx files so that they can dynamically link to the webservice depending on where in SharePoint it has been referenced. (all sharepoint webservices can be found in the sub directory of /_vti_bin/ of any site, for instance the web service webs.asmx can be found in both the url http://intranet/_vti_bin/webs.asmx and http://intranet/customersites/webs.asmx). When the wsdl and disco files have been properly modified to fit the SharePoint standard of handling this feature, the new web service has to be added to the file spdisco.aspx which is a directory of all web services that are available.

After a lot of hazel, I got this to work, and with a strong named assembly, deployed in the GAC and run in the SharePoint context. I finally got it to work the way I wanted it to.

So, if you also want your own web service in SharePoint. I would suggest following the walk-through very thoroughly and I have a few pointers. My web service was called WebsExtra.asmx, my class was called Service, and the assembly "WSTools.dll".

1. First, make sure the asmx-file works. Develop it using a normal web application. You should be able to address it. I had created a new web site using TCP port 8000 and hence tried: http://intranet:8000/WebsExtra.asmx. If that doesn't work, make sure you have strong named your assembly correctly, deployed it the the GAC (i.e. copied it to c:\windows\assembly) and addressed the class using the full strong name ("Service, WSTools, Version=1.0.0.0, Culture=Neutral, PublicKeyToken=037c5a828198ba1e" in my case).
   
2. Ok. That works. Good. Make sure the file also works when you placed it in the _layouts directory according to the walk-through. If not, you might still not be addressing the class with the full strong name.
   
3. After I created the files WebsExtra.wsdl and WebsExtra.disco, copied them to the ISAPI directory, renamed them to WebsExtrawsdl.aspx and WebsExtradisco.aspx, and modified them to be able to handle the dynamic linking that SharePoint uses, I made sure that I could really see the aspx-files using IE. I found them at http://intranet/_vti_bin/WebsExtrawsdl.aspx and http://intranet/_vti_bin/WebsExtradisco.aspx .
   Also check the contents of them and make sure they follow the same structure as similar files in the ISAPI directory (for instance Webswsdl.aspx and Websdisco.aspx, which you also can find using IE). Make sure that the referencing to the web service really uses the name you have set and not the name used in the walk-through.At the bottom of this entry is a copy of the files I used and a copy of the result I got in IE.
   
4. When both these files work, make the additions to the bottom of spdisco.aspx as well (within the discovery-tag though). This file can also be found using IE. You can probably guess it's url. Have a look at my version at the bottom of this entry, including the result in IE.
   
5. When I got that working, I now tried to access the addresses:
   http://intranet/_vti_bin/WebsExtra.asmx?wsdl and http://intranet/_vti_bin/WebsExtra.disco. These aren't actually files that you can find in the ISAPI directory but are mapped to the aspx-files mentioned in 3 above. You can check this by checking one of the out-of-the-box web services like Webs.asmx.
   
6. When you've got all these working properly, you should be able to add the web service as a web reference in some test project. (I usually use Windows Forms programs since they are the easiest to debug). If all has been set up properly, you should now be able to add the web service as a web refence. If the dialog gives you problems, it is usually due to errors in the wsdl or disco files. I had lots of these and was quite close to suicide but finally found them all. Most of the problems I had were due to the fact that I had used Visual Studio to edit the wsdl and disco aspx files. VS 2005 had been very "helpful" and had added ="" here and there, making the syntax erroneous. So, my suggestion, use notepad to copy paste the code from the walk-through. When that is done, you can use VS 2005 to modify the code.
   

   
    

WebsExtrawsdl.aspx

<%@
Page
Language="C#"
Inherits="System.Web.UI.Page"
%>

<%@
Assembly
Name="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
%>

<%@
Import
Namespace="Microsoft.SharePoint.Utilities"
%>

<%@
Import
Namespace="Microsoft.SharePoint"
%>

<% Response.ContentType = "text/xml"; %>

<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://tempuri.org/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://tempuri.org/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

<wsdl:types>

<s:schema
elementFormDefault="qualified"
targetNamespace="http://tempuri.org/">

<s:element
name="CreateSharePointSubWeb">

<s:complexType>

<s:sequence>

<s:element
minOccurs="0"
maxOccurs="1"
name="portalUrl"
type="s:string"
/>

<s:element
minOccurs="0"
maxOccurs="1"
name="subsite"
type="s:string"
/>

<s:element
minOccurs="0"
maxOccurs="1"
name="name"
type="s:string"
/>

<s:element
minOccurs="0"
maxOccurs="1"
name="Title"
type="s:string"
/>

<s:element
minOccurs="0"
maxOccurs="1"
name="Description"
type="s:string"
/>

<s:element
minOccurs="1"
maxOccurs="1"
name="templateId"
type="s:int"
/>

</s:sequence>

</s:complexType>

</s:element>

<s:element
name="CreateSharePointSubWebResponse">

<s:complexType>

<s:sequence>

<s:element
minOccurs="0"
maxOccurs="1"
name="CreateSharePointSubWebResult"
type="s:string"
/>

</s:sequence>

</s:complexType>

</s:element>

<s:element
name="HelloWorld">

<s:complexType
/>

</s:element>

<s:element
name="HelloWorldResponse">

<s:complexType>

<s:sequence>

<s:element
minOccurs="0"
maxOccurs="1"
name="HelloWorldResult"
type="s:string"
/>

</s:sequence>

</s:complexType>

</s:element>

</s:schema>

</wsdl:types>

<wsdl:message
name="CreateSharePointSubWebSoapIn">

<wsdl:part
name="parameters"
element="tns:CreateSharePointSubWeb"
/>

</wsdl:message>

<wsdl:message
name="CreateSharePointSubWebSoapOut">

<wsdl:part
name="parameters"
element="tns:CreateSharePointSubWebResponse"
/>

</wsdl:message>

<wsdl:message
name="HelloWorldSoapIn">

<wsdl:part
name="parameters"
element="tns:HelloWorld"
/>

</wsdl:message>

<wsdl:message
name="HelloWorldSoapOut">

<wsdl:part
name="parameters"
element="tns:HelloWorldResponse"
/>

</wsdl:message>

<wsdl:portType
name="ServiceSoap">

<wsdl:operation
name="CreateSharePointSubWeb">

<wsdl:input
message="tns:CreateSharePointSubWebSoapIn"
/>

<wsdl:output
message="tns:CreateSharePointSubWebSoapOut"
/>

</wsdl:operation>

<wsdl:operation
name="HelloWorld">

<wsdl:input
message="tns:HelloWorldSoapIn"
/>

<wsdl:output
message="tns:HelloWorldSoapOut"
/>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding
name="ServiceSoap"
type="tns:ServiceSoap">

<soap:binding
transport="http://schemas.xmlsoap.org/soap/http"
/>

<wsdl:operation
name="CreateSharePointSubWeb">

<soap:operation
soapAction="http://tempuri.org/CreateSharePointSubWeb"
style="document"
/>

<wsdl:input>

<soap:body
use="literal"
/>

</wsdl:input>

<wsdl:output>

<soap:body
use="literal"
/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation
name="HelloWorld">

<soap:operation
soapAction="http://tempuri.org/HelloWorld"
style="document"
/>

<wsdl:input>

<soap:body
use="literal"
/>

</wsdl:input>

<wsdl:output>

<soap:body
use="literal"
/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:binding
name="ServiceSoap12"
type="tns:ServiceSoap">

<soap12:binding
transport="http://schemas.xmlsoap.org/soap/http"
/>

<wsdl:operation
name="CreateSharePointSubWeb">

<soap12:operation
soapAction="http://tempuri.org/CreateSharePointSubWeb"
style="document"
/>

<wsdl:input>

<soap12:body
use="literal"
/>

</wsdl:input>

<wsdl:output>

<soap12:body
use="literal"
/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation
name="HelloWorld">

<soap12:operation
soapAction="http://tempuri.org/HelloWorld"
style="document"
/>

<wsdl:input>

<soap12:body
use="literal"
/>

</wsdl:input>

<wsdl:output>

<soap12:body
use="literal"
/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service
name="Service">

<wsdl:port
name="ServiceSoap"
binding="tns:ServiceSoap">

<soap:address
location=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
/>

</wsdl:port>

<wsdl:port
name="ServiceSoap12"
binding="tns:ServiceSoap12">

<soap12:address
location=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

 

When accessed at http://intranet/_vti_bin/WebsExtrawsdl.aspx or http://intranet/_vti_bin/WebsExtra.asmx?wsdl the following was the result:

 

<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://tempuri.org/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://tempuri.org/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

    <wsdl:types>

        <s:schema
elementFormDefault="qualified"
targetNamespace="http://tempuri.org/">

            <s:element
name="CreateSharePointSubWeb">

                <s:complexType>

                    <s:sequence>

                        <s:element
minOccurs="0"
maxOccurs="1"
name="portalUrl"
type="s:string" />

                        <s:element
minOccurs="0"
maxOccurs="1"
name="subsite"
type="s:string" />

                        <s:element
minOccurs="0"
maxOccurs="1"
name="name"
type="s:string" />

                        <s:element
minOccurs="0"
maxOccurs="1"
name="Title"
type="s:string" />

                        <s:element
minOccurs="0"
maxOccurs="1"
name="Description"
type="s:string" />

                        <s:element
minOccurs="1"
maxOccurs="1"
name="templateId"
type="s:int" />

                    </s:sequence>

                </s:complexType>

            </s:element>

            <s:element
name="CreateSharePointSubWebResponse">

                <s:complexType>

                    <s:sequence>

                        <s:element
minOccurs="0"
maxOccurs="1"
name="CreateSharePointSubWebResult"
type="s:string" />

                    </s:sequence>

                </s:complexType>

            </s:element>

            <s:element
name="HelloWorld">

                <s:complexType />

            </s:element>

            <s:element
name="HelloWorldResponse">

                <s:complexType>

                    <s:sequence>

                        <s:element
minOccurs="0"
maxOccurs="1"
name="HelloWorldResult"
type="s:string" />

                    </s:sequence>

                </s:complexType>

            </s:element>

        </s:schema>

    </wsdl:types>

    <wsdl:message
name="CreateSharePointSubWebSoapIn">

        <wsdl:part
name="parameters"
element="tns:CreateSharePointSubWeb" />

    </wsdl:message>

    <wsdl:message
name="CreateSharePointSubWebSoapOut">

        <wsdl:part
name="parameters"
element="tns:CreateSharePointSubWebResponse" />

    </wsdl:message>

    <wsdl:message
name="HelloWorldSoapIn">

        <wsdl:part
name="parameters"
element="tns:HelloWorld" />

    </wsdl:message>

    <wsdl:message
name="HelloWorldSoapOut">

        <wsdl:part
name="parameters"
element="tns:HelloWorldResponse" />

    </wsdl:message>

    <wsdl:portType
name="ServiceSoap">

        <wsdl:operation
name="CreateSharePointSubWeb">

            <wsdl:input
message="tns:CreateSharePointSubWebSoapIn" />

            <wsdl:output
message="tns:CreateSharePointSubWebSoapOut" />

        </wsdl:operation>

        <wsdl:operation
name="HelloWorld">

            <wsdl:input
message="tns:HelloWorldSoapIn" />

            <wsdl:output
message="tns:HelloWorldSoapOut" />

        </wsdl:operation>

    </wsdl:portType>

    <wsdl:binding
name="ServiceSoap"
type="tns:ServiceSoap">

        <soap:binding
transport="http://schemas.xmlsoap.org/soap/http" />

        <wsdl:operation
name="CreateSharePointSubWeb">

            <soap:operation
soapAction="http://tempuri.org/CreateSharePointSubWeb"
style="document" />

            <wsdl:input>

                <soap:body
use="literal" />

            </wsdl:input>

            <wsdl:output>

                <soap:body
use="literal" />

            </wsdl:output>

        </wsdl:operation>

        <wsdl:operation
name="HelloWorld">

            <soap:operation
soapAction="http://tempuri.org/HelloWorld"
style="document" />

            <wsdl:input>

                <soap:body
use="literal" />

            </wsdl:input>

            <wsdl:output>

                <soap:body
use="literal" />

            </wsdl:output>

        </wsdl:operation>

    </wsdl:binding>

    <wsdl:binding
name="ServiceSoap12"
type="tns:ServiceSoap">

        <soap12:binding
transport="http://schemas.xmlsoap.org/soap/http" />

        <wsdl:operation
name="CreateSharePointSubWeb">

            <soap12:operation
soapAction="http://tempuri.org/CreateSharePointSubWeb"
style="document" />

            <wsdl:input>

                <soap12:body
use="literal" />

            </wsdl:input>

            <wsdl:output>

                <soap12:body
use="literal" />

            </wsdl:output>

        </wsdl:operation>

        <wsdl:operation
name="HelloWorld">

            <soap12:operation
soapAction="http://tempuri.org/HelloWorld"
style="document" />

            <wsdl:input>

                <soap12:body
use="literal" />

            </wsdl:input>

            <wsdl:output>

                <soap12:body
use="literal" />

            </wsdl:output>

        </wsdl:operation>

    </wsdl:binding>

    <wsdl:service
name="Service">

        <wsdl:port
name="ServiceSoap"
binding="tns:ServiceSoap">

            <soap:address
location="http://intranet/_vti_bin/WebsExtrawsdl.aspx" />

        </wsdl:port>

        <wsdl:port
name="ServiceSoap12"
binding="tns:ServiceSoap12">

            <soap12:address
location="http://intranet/_vti_bin/WebsExtrawsdl.aspx" />

        </wsdl:port>

    </wsdl:service>

</wsdl:definitions>

 

And the file WebsExtradisco.aspx:

<%@
Page
Language="C#"
Inherits="System.Web.UI.Page"
%>
<%@
Assembly
Name="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
%>
<%@
Import
Namespace="Microsoft.SharePoint.Utilities"
%>
<%@
Import
Namespace="Microsoft.SharePoint"
%>

<% Response.ContentType = "text/xml"; %>

<discovery
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/disco/">

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request) + "?wsdl"),Response.Output); %>
docref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<soap
address=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
xmlns:q1="http://tempuri.org/"
binding="q1:ServiceSoap"
xmlns="http://schemas.xmlsoap.org/disco/soap/"
/>

<soap
address=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
xmlns:q2="http://tempuri.org/"
binding="q2:ServiceSoap12"
xmlns="http://schemas.xmlsoap.org/disco/soap/"
/>

</discovery>

 

And when I browsed the pages http://intranet/_vti_bin/WebsExtradisco.aspx or http://intranet/_vti_bin/WebsExtra.disco was:

 

<discovery
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/disco/">

    <contractRef
ref="http://intranet/_vti_bin/WebsExtradisco.aspx?wsdl"
docref="http://intranet/_vti_bin/WebsExtradisco.aspx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <soap
address="http://intranet/_vti_bin/WebsExtradisco.aspx"
xmlns:q1="http://tempuri.org/"
binding="q1:ServiceSoap"
xmlns="http://schemas.xmlsoap.org/disco/soap/" />

    <soap
address="http://intranet/_vti_bin/WebsExtradisco.aspx"
xmlns:q2="http://tempuri.org/"
binding="q2:ServiceSoap12"
xmlns="http://schemas.xmlsoap.org/disco/soap/" />

</discovery>

 

Of course, to make the address translation from http://intranet/_vti_bin/WebsExtra.disco actually point to the correct file http://intranet/_vti_bin/WebsExtradisco.aspx and similary http://intranet/_vti_bin/WebsExtra.asmx?wsdl point to http://intranet/_vti_bin/WebsExtrawsdl.aspx the correct setting have to be added to the file spdisco.aspx. This is the version I had (Notice the two last tags before the if-statement):

 

<%@
Page
Language="C#"
Inherits="System.Web.UI.Page"
%>
<%@
Assembly
Name="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
%>
<%@
Import
Namespace="Microsoft.SharePoint.Utilities"
%>
<%@
Import
Namespace="Microsoft.SharePoint"
%>

<%@
Import
Namespace="Microsoft.SharePoint.WebControls"
%>

<%@
Import
Namespace="Microsoft.SharePoint.Administration"
%>

<% SPSite spServer = SPControl.GetContextSite(Context); SPWeb spWeb = SPControl.GetContextWeb(Context); %>

<% Response.ContentType = "text/xml"; %>

<discovery
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.xmlsoap.org/disco/">

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/alerts.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/alerts.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/alerts.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/Authentication.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/Authentication.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/Authentication.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/copy.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/copy.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/copy.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/dspsts.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/dspsts.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/dspsts.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/dws.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/dws.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/dws.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/forms.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/forms.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/forms.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/imaging.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/imaging.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/imaging.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/lists.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/lists.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/lists.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/meetings.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/meetings.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/meetings.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/People.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/People.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/People.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/permissions.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/permissions.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/permissions.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/SharepointEmailWS.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/SharepointEmailWS.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/SharepointEmailWS.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/SiteData.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/SiteData.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/SiteData.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/sites.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/sites.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/sites.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/spsearch.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/spsearch.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/spsearch.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/UserGroup.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/UserGroup.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/UserGroup.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/versions.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/versions.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/versions.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/views.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/views.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/views.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/WebPartPages.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/WebPartPages.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/WebPartPages.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/webs.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/webs.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/webs.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<contractRef
ref=<% SPEncode.WriteHtmlEncodeWithQuote(Response, spWeb.Url + "/_vti_bin/WebsExtra.asmx?wsdl", '"'); %>
docRef=<% SPEncode.WriteHtmlEncodeWithQuote(Response, spWeb.Url + "/_vti_bin/WebsExtra.asmx", '"');%>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<soap
address=<% SPEncode.WriteHtmlEncodeWithQuote(Response, spWeb.Url + "/_vti_bin/WebsExtra.asmx", '"'); %>
xmlns:q1="http://schemas.microsoft.com/sharepoint/soap/directory/"
binding="q1:ServiceSoap"
xmlns="http://schemas.xmlsoap.org/disco/soap/"
/>

<%

    if (spServer.WebApplication is SPAdministrationWebApplication)

    {

%>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_adm/Admin.asmx?wsdl"),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_adm/Admin.asmx"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/scl/"
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_adm/Admin.asmx?disco"),Response.Output); %>
xmlns="http://schemas.xmlsoap.org/disco/"
/>

<% } %>

</discovery>

 

And when browsing to http://intranet/_vti_bin/spdisco.aspx I got the following result:

<discovery
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/disco/">

    <contractRef
ref="http://intranet/_vti_bin/WebsExtradisco.aspx?wsdl"
docref="http://intranet/_vti_bin/WebsExtradisco.aspx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <soap
address="http://intranet/_vti_bin/WebsExtradisco.aspx"
xmlns:q1="http://tempuri.org/"
binding="q1:ServiceSoap"
xmlns="http://schemas.xmlsoap.org/disco/soap/" />

    <soap
address="http://intranet/_vti_bin/WebsExtradisco.aspx"
xmlns:q2="http://tempuri.org/"
binding="q2:ServiceSoap12"
xmlns="http://schemas.xmlsoap.org/disco/soap/" />

</discovery>

<discovery
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.xmlsoap.org/disco/">

    <contractRef
ref="http://intranet/_vti_bin/alerts.asmx?wsdl"
docRef="http://intranet/_vti_bin/alerts.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/alerts.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/Authentication.asmx?wsdl"
docRef="http://intranet/_vti_bin/Authentication.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/Authentication.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/copy.asmx?wsdl"
docRef="http://intranet/_vti_bin/copy.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/copy.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/dspsts.asmx?wsdl"
docRef="http://intranet/_vti_bin/dspsts.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/dspsts.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/dws.asmx?wsdl"
docRef="http://intranet/_vti_bin/dws.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/dws.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/forms.asmx?wsdl"
docRef="http://intranet/_vti_bin/forms.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/forms.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/imaging.asmx?wsdl"
docRef="http://intranet/_vti_bin/imaging.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/imaging.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/lists.asmx?wsdl"
docRef="http://intranet/_vti_bin/lists.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/lists.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/meetings.asmx?wsdl"
docRef="http://intranet/_vti_bin/meetings.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/meetings.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/People.asmx?wsdl"
docRef="http://intranet/_vti_bin/People.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/People.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/permissions.asmx?wsdl"
docRef="http://intranet/_vti_bin/permissions.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/permissions.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/SharepointEmailWS.asmx?wsdl"
docRef="http://intranet/_vti_bin/SharepointEmailWS.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/SharepointEmailWS.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/SiteData.asmx?wsdl"
docRef="http://intranet/_vti_bin/SiteData.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/SiteData.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/sites.asmx?wsdl"
docRef="http://intranet/_vti_bin/sites.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/sites.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/spsearch.asmx?wsdl"
docRef="http://intranet/_vti_bin/spsearch.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/spsearch.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/UserGroup.asmx?wsdl"
docRef="http://intranet/_vti_bin/UserGroup.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/UserGroup.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/versions.asmx?wsdl"
docRef="http://intranet/_vti_bin/versions.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/versions.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/views.asmx?wsdl"
docRef="http://intranet/_vti_bin/views.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/views.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/WebPartPages.asmx?wsdl"
docRef="http://intranet/_vti_bin/WebPartPages.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/WebPartPages.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/webs.asmx?wsdl"
docRef="http://intranet/_vti_bin/webs.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <discoveryRef
ref="http://intranet/_vti_bin/webs.asmx?disco"
xmlns="http://schemas.xmlsoap.org/disco/" />

    <contractRef
ref="http://intranet/_vti_bin/WebsExtra.asmx?wsdl"
docRef="http://intranet/_vti_bin/WebsExtra.asmx"
xmlns="http://schemas.xmlsoap.org/disco/scl/" />

    <soap
address="http://intranet/_vti_bin/WebsExtra.asmx"
xmlns:q1="http://schemas.microsoft.com/sharepoint/soap/directory/"
binding="q1:ServiceSoap"
xmlns="http://schemas.xmlsoap.org/disco/soap/" />

</discovery>

 

So, with these example files, and these tips, I hope I can ease your troubles in making you own custom sharepoint web service.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se