There were a lot of promises and hopes, but did MS actually get around to including ASP.Net AJAX in either WSS3 SP1 or MOSS SP1? None of the release notes mention it...
No, ASP.Net AJAX is not included in either Service Pack.
ASP.Net AJAX was included with .net 3.5.
As far as I remember it wasn't included in WSS3 or MOSS SP1.
BTW WSS3 & MOSS SP2 is now out (and I don't believe it was included in that either.)
It's not that hard to get setup, you just need to make some interesting additions to your web.config, and master pages.
In my experience ASP.NET AJAX must be installed by itself (it hasn't been included in anything I have installed). Here is the download link for the installer.
Follow this article to get it loaded into the SharePoint web.config files.
Related
We have a common SharePoint server which runs an internal SharePoint site. Our teams deploy their SharePoint products in the server and add it to our site. Some products user .net framework 2.0 and some products use .net 3.5. So they enable ajax extenisons for the site for .net 2.0 which adds the entries for the assembly System.Web.Extensions version 1.0.61025.0 where as our version will be 3.5.0.0. Because of the difference we get an ambiguous error while running the web site.
How can we deploy different products using different versions of Ajax extensions in the same site?
You should upgrade all your servers to 3.5, any other workaround is useless now. If you still have to do that, I would compile everything under 1.0.61025 and add to the web.config of the servers running 3.5 entries mapping dll versions (just like they do in SharePoint 2007 for mapping DLL for web parts compiled under SharePoint 2003, take a look at the web.config, it's self-explanatory.
What is the best way to deploy a couple of asmx webservices to IIS. (6.0, 6.1, 7.0)
The services are an optional install and I think the most convenient way to install them would be some kind of Windows Installer package.
I created a small C# program that directly modifies the IIS Metabase, but this only works on IIS 6.0 and 6.1 and I don't want to ship something that might harm a customers IIS installation.
Our services (~10 different .asmx files) are all precompiled and organized in the following structure:
/services
/serviceA
/bin
Service.asmx
/serviceB
/bin
Service.asmx
/serviceC
/bin
Service.asmx
...
..
.
WiX is really best tool to do any kind of software deployment on the Windows platform. Among other things, it includes custom actions for this kind IIS configuring, see XML elements <iis:WebServiceExtension>, <iis:WebSite>, <iis:WebVirtualDir> and <iis:WebApplication> for details.
I did this a long time back (XP) using VBScript and the VS installer?
Id imagine there is a much nicer way to do this now
NerdDinner.csproj won't load in vs2008 sp1 with .net 3.5 sp1. Am I not up-to-date on these tools or something? It complains this project type not supported on this installation.
Do you have the ASP.NET MVC Framework installed? If not, you need it. NerdDinner is an example of an MVC Framework project, and you won't be able to open it or run it without the ASP.NET MVC Framework installed.
You can find the appropriate installation information at http://www.asp.net or more specifically http://www.asp.net/mvc
In my I had to change the value of the "ProjectTypeGuids" in the project file. I copied them from another MVC project that I had created with my version of VS 2008.
This is the post that gave me the answer:
http://www.stuffthatjustworks.com/How+To+Fix+Xcsproj+Cannot+Be+Opened+The+Project+Type+Is+Not+Supported+By+This+Installation.aspx
In my case...it was the wrong version of the framework.
I just copied the from another asp.net mvc project I had made. (then you probably have to fix up the references, which is trivial with resharper :-) )
As stated here, the way evidence is loaded will change in .NET 4.0. How will this impact systems like SharePoint where you can specify exactly which permission will be granted for a dll in the wsp-package? Isn’t SharePoint using AppDomain.ExecuteAssembly(Name,Evidence) internally to make this possible, or am I missing something?
.NET 4.0 won't be used for SharePoint until the release after SharePoint 2010. We will still be on .NET 3.5 until then. So perhaps revisit this issue at a later date.
I'm deploying a webpart on sharepoint and getting some errors. The webpart consumes data from a Web Service and displays a chart using Microsoft Chart (Framework 3.5). When I try to acces it, I get the folowing error:
Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
StackTrace: at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
I tried copying System.Servicemodel.dll to the bin folder and registering it on the GAC, but the error does not change.
Any idea?
Thanks
To expand on the above answers:
It does sound like your site is running on asp.net 2.x. Being that System.ServiceModel is a 3.x component, the assembly will not load. You will need to install 3.5 on the server, or if you already have it set IIS to run the site under 3.5
I had a similar problem, but it was because my .NET framework got messed up/corrupted, so I'll post what fixed it for me. Maybe it's overkill, but it worked when nothing else would.
Get the “dotnetfx_cleanup_tool” from http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx (I think one of the download links fails, so use the other one)
Uninstall frameworks 2.0 and above (I did 3.5, 3.0, 2.0. 2.0 made me reboot).
IMPORTANT: Go to C:\WINDOWS\Microsoft.NET\Framework and delete or rename the folders for the versions of .NET you removed.
Then I installed .NET Framework 2.0 SP2 (reboot afterwards). The error was gone.
I also installed .NET Framework 3.5 SP1 (works without rebooting) and the error was still gone.
Is your website configured to use ASP.NET 2.0.5.something ?
Maybe this article can be helpfull:
Forcing ASP.NET 3.5 ON IIS
Try installing .NET Framework 3.5 on your sharepoint server.
It sounds like the Web Part itself was built against an older version of the System.ServiceModel assembly (probably a beta version). If you have access to the web part's source code, you should recompile it against the latest stable version. Otherwise you'll have to find the exact same version of System.ServiceModel and register that into your GAC.
EDIT: You could also try going into your web app's Web.config and replace your System.ServiceModel reference with this:
<Reference Include="System.ServiceModel">
<SpecificVersion>False</SpecificVersion>
</Reference>
The problem was within the Web Service, not the webpart.
The machine where the web service was deployed has framework 2.0 installed.
The exception was catched on the webpart and reported back.
Thank you all for your comments.
fire up your Visual Studio 2010 Command Prompt or browse to "C:\Windows\Microsoft.NET\Framework\ v4.0.30319". And run the following command from the command prompt:
aspnet_regiis.exe -iru
I came across this same problem with a Silverlight 4 app and solved it by switch off Debug Exception checks for
Common Language Runtime exceptions
in Debug => Exceptions
Hope that helps
Mike