I recently started to use AjaxControlToolkit v3.0.30930.0 in my application together with System.Web.Extension 3.5.
My development environment is Visual Studio 2005, .NET Framework 2.0 and the development language is C#.
The Ajax control I used is the ModalPopupExtender. I also used the UpdatePanel and updateprogress controls.
Everything is working fine on my development machine. But I got a problem after I deployed the application to a server which does not have System.Web.Extension 3.5 installed, which is understandable.
My question is, can the ajax controls I used work without System.Web.Extension 3.5? Say I revert the ajaxcontroltoolkit back to version 1.0.61025.0? I don't have the option to install .NET 3.5 as yet.
Thank you for your help.
John
I figured out a solution to my question.
Here is what I did.
I set my project to reference version 1.0.61025.0 of system.web.extension dll and version 1.0.20229.20821 of ajaxcontroltoolkit. Then I updated all the relevant settings to tell .NET runtime to load version 1.0.61025.0 of system.web.extension dll. It worked out fine.
Hope this is of some help to somebody.
John
Related
My existing code work as expected with .net framework 4. But after upgrade to .net 4.6. Its not work
I also ran into this. Had to uninstall all 4.6 frameworks, and then re-install 4.5.2 Framework. And finally re-register in IIS by running aspnet_regiis -i
and then my CR started working again.
So removing 4.6 for Windows 2008 Server is the solution. For Windows 2012 Server, turns out the 4.6 is "hidden" as update KB3102467 that was pushed out around April 2017. Uninstalling that got the Crystal Reports viewer working again on our Windows 2012 servers.
Another answer for anyone... fix is simple but requires a manual change every time their is a patch\update for .NET Framework 4.6
Turns out the problem is that Crystal Reports looks for a folder that matches the version of the Framework including the "build".
The quickest way to manually fix this is go to the web page that has the Viewer and look at the source. You will find a line similar to /aspnet_client/system_web/4_6_xxx/crystalreportviewers13.....
Go to the servers hard drive and rename\copy that folder to the version it is looking for and you are back in business.
I started using Blue Mix, and download starter code, but once i tried to compile that in VS 2015, its showing me library not found..
Can someone help with that ?
Rakesh Yadav
The ASP.NET 5 starter code in Bluemix is currently written for the beta3 release and VS may now be trying to use the newer beta4 or beta5 releases. Normally you can change that under your project's properties, but given the major changes between beta3 and beta4 (it wasn't even called DNX in beta3) I don't think it's possible to compile the starter code with the latest VS. The older getting started instructions point to http://go.microsoft.com/fwlink/?LinkId=527980 for VS, I would suggest trying that for now.
I have downloaded and installed the Entity Designer Starter Kit on both VS 2010 and 2012. I've created a project and have customized that project to allow me to add (for now) three attributes for each field value: See Below: (I'd post the image but I've only started posting here and I don't have 10 points) :(
As you can't see above, the Extension is working...on VS 2010, however, we need to use VS 2012 - so we can have the new support for geography fields in our Model, but it doesn't seem to work in VS 2012. The extension shows up as an installed extension in the Extension Manager in both versions, but doesn't work (or do anything in 2012.) when we build a new Model or open an existing one. :(
I've looked at the manifest for versioning info, and it DOES show up in the Extension Manager as having been installed (in both versions). (See part of Manifest below -- We are using the Professional version of 2012)
<SupportedProducts>
<VisualStudio Version="11.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
<Edition>Express_All</Edition>
</VisualStudio>
<VisualStudio Version="10.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
<Edition>Express_All</Edition>
</VisualStudio>
</SupportedProducts>
Does anyone have any idea why its not running in 2012?
Thanks for any help!!!!!!!
bob
Back in 2010 I found that the Starter Kit did not work, perhaps due to the version being for VS2010 RC.
So I rebuilt it, and today, I've just upgraded it to VS2012.
So you can get it from my Blog.
All I did was run it though the VS upgrade wizard, and then change the manifest to VS2012 and it worked fine. Perhaps you could explain a little more "geography fields", as I've not read up yet on any of the changes in VS2012.
http://www.jsrsoft.co.uk/blog/post/Entity-Framework-Starter-Kit-alternative
Does anybody have successfully working module in DNN 6 with the Ajax Control Toolkit?
My modules stopped working when we migrated from DNN 5.x to to 6.x.
Modules compile without errors but I am getting client side script error:
'AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll'
Seems like this is conflict with Telerik's controls, according to information that I have found. But I didn't find any info how to fix it.
You should be able to use older versions of the ASP.NET AJAX Control Toolkit, but once they start requiring the ToolkitScriptManager, you're out of luck with DNN (though you'll be out of luck with any version of DNN, since there's not a way to override the type of ScriptManager it uses.
Starting with DNN 6, they use Telerik's RadScriptManager. Previously, you could modify the core code to switch out for the ToolkitScriptManager, but now switching out might cause other issues.
It could work together, but you'll need do some modifications to the core of DNN.
Here the list of things to do:
Check that you're using latest version of .Net 4.0 binaries of AjaxControlToolkit (I was able to let it work for DNN 6.0.1 with Telerik 2011.01.519 and ACT September 2011 v4.1.50927)
Check that in your web.config you have assembly binding redirects for System.Web.Extensions and System.Web.Extensions.Design to the version 4.0
Take DNN source package, find Library\Framework\AJAX.cs, locate method AddScriptManager, instantiation of RadScriptManager in it, for the version 6.0.1 look into line 54. Add one more property initializer:
EnableScriptCombine = false. Compile it (in Release configuration, of course), take DotNetNuke.dll and drop into your DNN installation.
You should be done.
Credits goes to Telerik support, despite it's stated there that it should work out of the box starting from 2010.1.625. Not sure, did I get them wrong, or they just reintroduced this bug.
P.S. DNN support promises to release version 6.1.0 in November with updated Telerik controls, which should fix this issue, at least on their opinion.
Just checked with nuke 6.1 and the last version of jaxcontroltoolkit - still the same error.
It looks like it's not supported anymore. Sad:(
I have downloaded the ASP.NET MVC 2 Release version (using Web Platform Installer) as well as the downloading the file directly from the link in WPI. No error messages are reported after the install.
When I go into Visual Web Developer and select Create New project I only the project reference to ASP.NET MVC version 1.0 and not version 2 (for clarity I have all the other project types, this is just in reference to the MVC projects).
I have restarted, uninstalled and restarted and installed my PC multiple times and it still won't play.
When clicking add a reference I can see the MVC.dll version 2.0.0.0 and add that no problem, but cannot manually upgrade the project since the ProjectTypeGuid used is not recognized.
For reference I am using Visual Web Developer 2008 on Windows XP. ASP.NET MVC version 1.0 is working fine and without issue.
Hope someone else can help.
DNH
I've installed MVC2 (VWD Express) on 3 computers now and 2 of them (Windows 7 and XP) have done this. I fixed both of them by uninstalling MVC1, MVC2 and VWD, then reinstalling via the Web Platform Installer. MVC1 is gone from WPI by the way. You can still download it from MS though. Could be just luck, but like I said, this worked twice for me.