I'm having a little trouble with my panning functionality in my Dev environment. The way I implemented panning functionality adding JQuery to drag an image behind a panel control. The panning functionality is available after zooming into the image. So I zoom into the image with zoomin/zoomout functionality, then I pan or drag the image behind the panel control. This works great in my local environment and even when I deploy the website to my local IIS. However, when I deploy to the Dev server, the image does not stay behind the panel control or is not contained within it. Are there any suggestions on what might be causing this? Below is some information on approaches I've tried.
I did a comparison on the two environments.
Configuration on my local environment:
.NET Compact Framework 2.0 SP2 (Version 2.0.7045)
.NET Compact Framework 3.5 (Version 3.5.7283)
.NET Framework 4 Client Profile (Version 4.0.30319)
.NET Framework 4 Extended
.NET Framework 4 Multi-Targeting Pack
AJAXControlToolkit: Version 3.5.50508.0
Configuration on Dev Server:
.NET 2.0: .NET 2.0 SP2 (Version 2.2.30729)
.NET 3.0: .NET 3.0 SP2 (Version 3.2.30729)
.NET 3.5: .NET 3.5 SP1 (Version 3.5.30729.1)
AJAXControlToolkit: Version 1.0.20229.0
Could it be that the slight mismatch in versions is causing the problem? I was thinking of somehow matching the .NET versions on my local machine to that of the dev server. Would this cause an issue? Also I am using Visual Studio 2008 Team System SP1 for development.
I tried adding the AJAXControlToolkit.dll file to the Dev server, but I get the same results.
I tried setting the panel control to style="overflow:hidden", but that didn't seem to work either.
Here is the piece of code I think is causing the problem:
<div id="draggable" style="position:relative;" onmousedown="makeDraggable(); return false;">
<img id="myimage" src="[path to image]" usemap="#circles" onmouseover="changeToHand()" />
</div>
</asp:Panel>
Any help is greatly appreciated!
The issue was isolated to IE. Mozilla and Chrome were fine. So I went to the configuration on IE and realized compatibility view settings were on. If you are on an intranet, make sure the compatibility view settings are off for that too.
Related
How do I get BrowserLink to work in MVC6 - using RC1 Release 1. Using Visual Studio 2015 Update 1.
Browsers never appear in Browser Link dashboard. No extra js is injected or extra web calls made by site so it just seems to not be adding browser link code.
I have app.UseBrowserLink(). I am running in Development mode, debug. I have tried CoreClr and Full Framework. This happens even with a brand new Asp.net 5 web template with no changes made to it.
What else do I need to do? Does Browserlink actually work for anyone with ASP.NET 5 RC1?
I would also add I ran older projects based on MVC5 and Browserlink works on them without issue.
Seems to be an issue with the installation of "Microsoft ASP.NET 5 RC1 Update 1". Go into Control Panel > Programs and Features > Click "Microsoft ASP.NET 5 RC1 Update 1" and press Change > Repair.
Fixed it for me on three of my development machines.
I have one web application in C# which is developed using Visual Studio 2010 and I want to convert or Migrate that web application in Visual Studio 2013 (C#).
Note:- Below listed things I used in my current Web Application using VS2010 (C#)
Asp.Net Server Controls.
ClassLibrary (.dll).
Web services.
Above Listed things I used in my current Web application which is in VS2010.
Now, My Question Is- What would be the major changes I would be facing if I am using all above listed Microsoft Technologies using C# and Migrate it to VS2013.
The biggest change for us was that Visual Studio Setup Project was depreciated in VS 2012, so we had to build new installers.
http://blogs.msdn.com/b/visualstudio/archive/2013/08/15/what-s-new-in-visual-studio-2013-and-installshield-limited-edition.aspx
Also, which version of .NET is you application? Keep in mind framework targeting for Visual Studios (basically if your application is .NET 3.5 SP 1 or newer you should be fine):
https://msdn.microsoft.com/en-us/vstudio/dn250998.aspx
The Web Services should also be okay, if you intend to keep creating web services instead of switching to WCF, you may want to look at this:
Create a asmx web service in C# using visual studio 2013
The thing we first noticed is VS2013 uses IIS Express 8.0, at the time our production web server was IIS 6 - we encountered, on numerous occasions a web.config setting working fine locally but forgot to add the IIS 6 equivalent.
For our web apps we kept targeting the same .Net framework and I can't recall any issues. For your reference our stack was Asp.Net MVC 4, EF 5 WebApi plus numerous NuGet packages. So we didn't have any asp.net server controls.
You may also want to ensure all your VS2010 plugins have a 2013 equivalent.
You shouldn't have any problem at all with the types of proyects you are using.
You could even open the solution with VS2013 and then open it back with VS2010 SP1 without any problem (as long as you don't switch the .NET framework to 4.5).
Starting from VS2012, Microsoft made changes to allow developers open a solution with older versions of VS (VS2010 SP1 being the oldest version that supports this). There ARE some proyect types that won't be compatible, but from the things you listed, you won't have any problems.
When you open the Solution with newest VS, it WILL make some changes, but you still will be able to open it with VS2010 SP1 (again, with some exceptions).
https://msdn.microsoft.com/en-us/library/hh266747.aspx
http://blogs.msdn.com/b/webdev/archive/2012/08/22/visual-studio-project-compatability-and-visualstudioversion.aspx
Anyway, my suggestion is, install VS2013 in a test machine and try it out. You can even create an Azure VM with VS2013 PreInstalled in minutes to try it out.
There is already available VS2015 preview, why not wait until it is released? (or use the preview)
https://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs.aspx
as other said, it should not brake much
I have a quick question concerning creating an web forms application with visual 2013 express. I'm working on older servers (Windows 2003) which cannot handle anything greater than .NET 4.
When I go to create my application with visual studio 2013 I go to the Visual Studio 2012 tab, where MVC 4 is listed and choose the web forms application there. What I've learned though, is that it automatically sets the framework to 4.5 still, so I have to change it to 4. In doing so, the NuGet packages get messed up and I have to reinstall them all. I discovered after reinstalling them all it's still messed up and I'm getting build errors. I assumed because I choose to use an older version of webforms, it would automatically set my framework up for me as well. Doing a little troubleshooting I discovered that even when you choose to create a MVC 4 application it still sets the framework to 4.5 and messes everything up when you try to change it.
I'm thinking about just downloading an older version of visual but I don't have admin rights to my computer and that is a pain. Any insight?
I'm painfully new to this material, so everything in layman's terms is appreciated!
when you select MVC 4 Web Application, or any of the other templates, there is a drop down at the top that allows you to select which Framework you would like to use. I'm using professional, it may be different in express.
http://msdn.microsoft.com/en-us/library/bb398202.aspx
I am using crystal report v10.5 with visual studio 2008 to develop crystal reports.The problem I am facing is with the toolbar which is not visible on Firefox but it is visible on IE and Chrome.
I have installed same version on both development machine and on production server which is Crystal report v10.5. My development machine is Windows 7 32bit and production is Windows 2008 64bit.
I have tried solutions mentioned on numerous forums such as
Copy the 'aspnet_client' folder from 'C:\Inetpub\wwwroot' to 'C:\Inetpub\wwwroot\your-website-name'.
create a new virtual directory in your web site and point it to "C:/Inetpub/wwwroot/aspnet_client".
Application pool is to be changed to "Classic" instead of "Integrated".
Set the application pool of your application to operate under LOCAL SERVICE permission.
But still I am not able to show toolbar on Firefox.
Configurations:
Visual Studio 2008
.Net Framework 3.5
Crystal Report for runtime 10.5
Windows Server 2008 64bit
Can anyone point me to the right direction?
Edit- I recently upgraded from Windows 2003 to Windows 2008 and the same version for CR 10.5 was working as expected without any mentioned solutions above.
Thank you
You need to add ClientTarget="uplevel" to the page directive of the aspx file.
<%# Page ClientTarget="uplevel" ... %>
It seems that there are compatibility issues between CR and certain browsers depending on the version of CR. There is a very helpful post here that has links to a compatibility table. I suggest to check that out and then see if you can maybe upgrade to a different version of CR.
Hope that helps.
My application use last Crystal Runtime on x64 server and work on firefox too.
1) If the toolbar is not visible there should be a reason (press F12 in firefox.. what do you see? 404 error? 500 error? Please post it!)
2) Crystal Reports Runtime 13.x IS available for X64 servers too.. There is no reason to use an old runtime containing many bugs resolved in other releases.
You can get it here (get MSI 64 bit - Support Pack 8)
After updating runtime you have to copy the 'aspnet_client' folder again fi you did (new virtual directory in your web site is a better approach)
After updating runtime you could need a little hack to let an application developed with older dll work with new dll. There are few rows you have to put into web.config described here.
After upgrading our web application to .NET 3.5 we noticed a strange issue with the Wizard control. Usually after IIS is restarted and a page with the control is loaded, the left hand navigation pane will not be displayed. Hitting this page again will solve this issue. It is also visible in dev environment, although it is intermittent and I don't have a reproducible sequence of steps. Has anybody else experienced a similar issue?
No changes were made to the wizard control in framework 3.5 so it's nothing to do with updating the framework