Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Can i upgrade my existing website from asp.net framework 2.0 to 4.0, is there any harm in doing that? and if i can do that without harming my current website than please tell me the required steps to achieve this target.
thanks in advance.
There are some breaking change if you move to asp.net ver 4
Meaning that you may need to change few things, and evaluate all the pages to see that they still working the same way.
I've always updated my projects through using newer versions of Visual Studio. So for example I'd quite a few projects created in VS 2005 which I then opened in VS2010. VS prompted me to upgrade to the newer .net version and took care of the process for me. Never caused any problems although I stopped it from messing with the web.config etc. which it asks about after doing the conversion.
You should have no big issues except for web.config entries specific to .NET 2.0.
On your application server, you may need to set "Classic mode" insted of "Integrated pipeline" if you experience further issues.
There's no harm in trying. There may be some changes required to your code. Just create a copy of your existing code and attempt to upgrade the copy. Based on that, the decision to go forward with an upgrade is up to you.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I am very new to DOT.net frameworks.
Shouldn't we always update to the latest release?
List Entity framework or identity framework .. all those frameworks ... why do we keep them around? just use the latest ones.
In fact, I am just starting to develop an asp.net website with RestAPIs, login, register, social login...
I wonder what is the best framework version (4.5) to use
From a large company point of view. You can not always technically get the latest version of .NET on your servers that store your applications. For some you have to go through a series of procedures to get everything to the latest so it's not necessarily developers that can trudge through this when you have a separation of duties like developers, system admins, etc. Although it's highly suggested to use the latest and greatest. Every dev/company has their own way of actually getting the most up-to-date versions of pretty much anything.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
If i am testing windows based project and my documentation is according to windows based and suddenly i have to migrate my windows based project into web based project according to need.
What different approach should i follow if i have all the documentation and test strategy for windows based project ?
Is there any change in test cases and test strategy?
Can i have few suggestion regarding this, what should i change and what different approach i need to bring in my testing.
I am changing my windows based project online examination into web based project.
I have some suggestion.
Well U have to perform Usability testing, Security testing , Browser compatibility testing.
U have to also check temporary data storage whenever your site lost connection with server.
Hi Perform load testing on your application and security testing. Also test this on mobile browsers.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am having an requirement to add a project into the existing one. Existing one is MVC 4.0 and using Dot net framework 4.5 application and is using DBML (Linq to SQL classes). The one which I want to add is using EDMX in Dot net Framework 4.0.Edmx is also of lower version. Versioning problem is solved by explicitly defining in Web.Config File. But the thing is both of the projects are building successfully but throwing exception at run time and the exception is ::
Schema specified is not valid. Errors:
App_Code.Model.csdl(3,4) : error 0019: The EntityContainer name must be unique. An EntityContainer with the name 'calendarEntities' is already defined.
and this is coming for every controller where it is being used.
Please help me As I am not clear with how to get rid off this error.
Just because there are specific instances where different versions can be supported, when used incorrectly trying to make mismatched versions of things can lead to what is essentially an unsupported project. This is because mismatched version configurations are not extensively tested and even if you were to call Microsoft support the first thing that they would tell you is to upgrade all of your projects to the same version of the runtime. So that is what I would recommend and if you have a specific issue please post the code and enough of the error so that help can be provided.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm an asp.net developer, but I haven't found a good workflow for deployment. Especially for small quick fixes that might not even require compiling.
The way I work now is to have two VS instances up while copy pasting a lot of code and files between the project and the folder on the IIS server. Is there an automated process that moves changes as I save in the VS project?
Generally speaking, what you are doing is a pretty big no no for a lot of reasons.
When you make changes one of the big advantages ASP.Net has over something like PHP is simply that obvious problems (like misspelling a variable name) are caught during the build phase. This is a huge benefit.
Next, if you are simply modifying a file and copying it's content to the server then it sounds like you are doing your testing in production instead of leveraging your local debugger. Again, very bad practice.
Finally, VS includes a publish command. The purpose of this is to compile and publish your site to the server. It can do so through the regular file system, FTP, web deployment packages or even FPSE. That last one is NOT recommended and is probably kept for backwards compatibility only.
Point is, develop and test locally. When your ready for it to go to the server, use the publish command.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 14 years ago.
Improve this question
I'm at my wit's end here. I'm trying to use an auto-complete extender from the asp.net ajax extensions toolkit, which is filled from a bog-standard webservice. The application is a .net 3.5 web site, hosting the webservice in a subdirectory (real, not virtual).
Whenever I try to post to the webservice I get the following error:
The HTTP verb POST used to access path '/Workarea/webservices/FindAdvisorNameService.asmx/FindAdvisorName' is not allowed.
To complicate matters, a co-worker of mine pulled down the solution and can run it fine.
After doing some Googling, it seems that there are some issues with URL rewriting, so I had him try using my web.config -- he still has no problem, and I still have no success.
Anyone have any thoughts on what could be up, or where to start looking?
To complicate matters, this is an Ektron CMS400.Net solution, but he has the same version of Ektron installed that I do. The project was recently upgraded from the 2.0 to 3.5 framework, but still, it's in 3.5 on his machine as well.
I've checked the IIS mappings, and GET, POST, and DEBUG are allowed on ASMX files.
Help me Obi-Wan KeSObi, you're my only hope!
Edit: Oh, yeah, to complicate matters, this is a brand new machine I have, so there's not likely to be that much weird stuff in the registry, etc. etc.. The co-worker's machine is almost as new.
Ok, found the issue with the help of a colleague. Seems the Ektron CMS added a mapping in IIS -- it mapped * to aspnet_isapi.dll. That overrode all the other mappings. I deleted that, and now things work.
Are you rewriting URLs? You need to exclude your web services from rewrites.