This is a general question about dealing with URL Rewriting in a development environment. I'm developing a CMS to learn ASP.NET/C#, and I will of course need to implement URL Rewriting. This technique is known to me since I've been using with PHP for several years. However in PHP, you can have a local HTTP server, modify the PHP content directly, refresh the page and see the results. Of course in ASP.NET it's not exactly the same, since you need to compile and then publish the code. The problem I have is that I need to check the URL Rewriting-friendly links my code will generate in my development environment - basically, make the ASP.NET Development Server compatible with URL Rewrite. Or maybe not. My question really is: what is the best solution to do that? Use IIS/Apache2 (w/ Mono) for the development server?
I've inherited a website which has been developed for IIS server. The hyperlinks in this website have a href attribute with the human readable form that appears in the url in the browser's searchbar.InApplication BeginRequest(), there is a method which will convert this into the acutal location of the page within the website's file structure.This works fine when running the website on IIS. However, when I am using the ASP.NET development server,the links do not work and I get a page not found error.I have noticed that Application_BeginRequest() is never called for the links when run using the ASP.NET development server. I have read that the ASP.NET development server will not serve pages that are outside of the application scope (http://msdn.microsoft.com/en-us/library/58wxa9w5%28VS.80%29.aspx),as the human-readable urls would appear to be when first processed by the server.Bear in mind that the urls in the aspx files are in human readable form, so I can't just use ResolveUrl(), because they don't correspond to files in the internal file structure until they have been re-written.I want to get the website running on the ASP.NET development server so that I can test it locally on my machine, which I can't really do if I can't get the url re-writing to work.
At our company we are going to develop more for the Windows platform than we have done up until now. As this scale of Windows development is new to us it would be nice with some feedback from experienced developers. Requirements we have: 5 developers from the beginning. 15 developers a year from now. All developers should be able to develop at the same time. Be able to develop solution for ASP.NET and EpiServer 5. Our idea:
A shared server which developers use for development through Terminal Services. SQL Server Express. Start with some free express edition of Visual Studio, upgrade to a commercial version if we need the additional features. Use IIS and not the web server built into Visual Studio. Questions:
Are we on the right track?
In terms of license costs the above should be cheapest, right?
What do you think about multiple developers doing development using a shared TS-server?
Do you know of any company which has a similar development environment?
Are we going to miss some features of the full Visual Studio version immediately? Is using Express version a bad choice? Is IIS the best choice? If use IIS the developers may use the same port for deployment. If we use the built in web server each one has to set their own port as we're sharing a machine.
Comment answer: We are thinking about a shared server as it will most likely decrease the license costs. So it's purely a cost issue. We are using CVS for version control. Our situation is that we develop on Mac and Linux, that's why buying 1 server license + Visual Studio licenses seems to be a cost effective way of starting this type of development.
My dev team and I would like to setup a development environment for our ASP.NET projects. BY development environment i do not mean Visual Studio. I mean, that we have a Database Server, a Application Server and a Web Server in a 'Development Environment'. We want to use this as our integration environment. Where the developers all work on there parts of ASP.NET Applications and then we can push our new changes up to test them as a whole. My Question is , what is the best way to deploy our code together without stepping on our toes?
I'm from PHP background. I used to use Apache, MySQL and PHP for web development. I'm just starting asp.net mvc. I've Visual Studio 2008 Pro SP1 & .NET 3.5 SP1 already installed on my computer. So, I installed ASP.NET MVC 1.0 Created a "ASP.NET MVC Web Application" project when I hit F5 it gives error Unable to connect to the ASP.NET Development Server No wonder. In this process I didn't setup the webserver. Can I use apache here? I guess IIS is the default. Where is it? How do I configure it? What is the WebRoot directory for IIS server? Where can I find it? On searching for "Unable to connect to the ASP.NET Development Server" I found this solution:
Step 1: Select the "Tools->External Tools" menu option in VS or Visual Web
Developer. This will allow you to configure and add new menu items to your Tools menu.
Step 2: Click the "Add" button to add a new external tool menu item. Name it "WebServer on Port 8010" (or anything else you want).
Step 3: For the "Command" textbox setting enter this value: C:WINDOWSMicrosoft.NETFrameworkv2.0.50727WebDev.WebServer.EXE (note: this points to the web-server that VS usually automatically runs).
Step 4: For the "Arguments" textbox setting enter this value: /port:8010 /path:$(ProjectDir) (or any port you like)
Step 5: Select the "Use Output Window" checkbox (this will prevent the command-shell window from popping up. Once you hit apply and ok you will now have a new menu item in your "Tools" menu called "WebServer on Port8010". You can now select any web project in your solution and then choose this menu option to launch a web-server that has a root site on port 8010 (or whatever other port you want) for the project. You can then connect to this site in a browser by simply saying [URL] All root based references will work fine.
Step 6: The last step is to configure your web project to automatically reference this web-server when you run or debug a site instead of launching the built-in web-server itself. To-do this, select your web-project in the solution explorer, right click and select "property pages". Select the "start options" setting on the left, and under server change the radio button value from the default (which is use built-in webserver) to instead be "Use custom server". Then set theBase URL value to be: [URL] But there is no C:WINDOWSMicrosoft.NETFrameworkv2.0.50727WebDev.WebServer.EXE such file on my system. Did I forget to install something?
EDIT:
I'm using Windows XP SP2 and logged in as a user with Administrative previlages. from this [URL]
Disable IPv6
Done
Make sure there isnt an edit in the hosts file for localhost There is no single entry in my hosts file (%SystemRoot%system32driversetchosts) with 'localhost' in it. Check firewall/virus settings to allow connections to/from devenv.exe I tried by disabling the firewall/antivirus If you can preview in the browser make sure the URL in the browser uses the same port number as the port number shown in the ASP.NET dev server taskbar icon. No, Actually there is no such dev server taskbar icon. Try setting a fixed, predefined port in project properties Tried it. But no positive result. S
Solution:
After trying everything. I came to conclusion that WebDev.WebServer.exe may be corrupt. So, I've replaced C:Program FilesCommon Filesmicrosoft sharedDevServer9.0WebDev.WebServer.EXE with a fresh copy : [URL]
I would like to know the method of setting up sub-domains in the development environment. Don't have any hosting account yet. But would like to test it up internally by simulating a similar setup that would be provided by the hosting company later on.
This question is for ASP.NET and SQL Server developers. What are your best practices with respect to setting up your development and test environment? I'm interesting in the following issues: How many tiers do you recommend and what goes on on each tier? Just dev, test, and production or perhaps dev, test, staging, and production? Which types of applications and/or servers should run on actual physical hardware and which can get away with a VM? What are your strategies for loosely coupling users from web sites, web developers from their web/app/DB servers, and DB developers from their DB servers?
How do developers stay "DRY?" What are the pros and cons to putting web, app, and DB servers on their own machines? Does putting servers on separate machines in order to minimize contention for a machine's resources trump any NIC and network latencies that might be introduced by putting them on different machines? How do you configure your web apps to minimize contention for resources (e.g. virtual directories, separate application pools, etc.) How and how often do you refresh your databases on each tier? Do you just refresh the data or both the data and objects?
I am working to rebuild my company's dev/test/QA environment. We have 10-15 programmers that are involved in a number of projects. They currently all develop locally on their PCs and use the dev environment for testing. We currently do not have a QA environment, so deployments are frequently a pain because bugs are usually found after something has gone live. Here's what I envision:
Doing away with everyone's local admin privileges and making everyone develop on a dev server. Create a QA environment that is identical to our production systems. This will allow them to test deployments. Create a new test environment that is more locked down than the dev server so that proper testing can be done. What are your thoughts? What is the best way to set up an environment like this? We develop ASP .NET applications using MS Visual Studio 2008.
I'm in the process of setting up a project's development environment from scratch. My company has used various technologies, but this is the first time we're able to focus on the development environment for a .NET project from the ground up -- and I'm the lucky guy who gets to make it work.
I'm actually very excited to do this, as it has the potential to become a pattern for repeated success across multiple projects.
I'd like your help to assess the build process that I'm using and shout out where I may find myself running into issues.
So, here goes--
Server Side:Windows Server 2008 SQL Server 2008 (relatively small / low traffic DB, wasn't worth devoting a separate VM in dev) VisualSVN for hosting source code (just easier to manage on Windows), Trac hooked into VisualSVN for wiki/bugs/tracking NAnt for automatic builds / running unit tests FxCop (potentially) as another set of tests from CruiseControl to check framework best practices CruiseControl.NET for continuous integration, to automatically call the NAnt build and run NUnit / FxCop tests when new source is committed. Dev Machines / Tools:VS 2010 NUnit CSLA (potentially) to use in developing our business logic layer NHibernate or Entity Framework (potentially) help facilitate OR/M
we're a team of three old c++ developers now developing web apps for the very first time. the web app is in asp.net using vs 2005, the db is sql server 2005. application is on a shared folder on a development server running win server 2003 - no solution or project just a folder structure. developers access this shared folder to develop the pages using xp. after a planned development iteration is finished the test server is updated for test cycles.
for deployment we just copy the web pages over to the production server's virtual dir. pretty primitive i guess :) but its been working that way for a while. after we have taken over we want to know what'd be better way for web dev in team. we also want to get the team using source control. the outfit has an old cvs server so no chances for old or new team foundation.
I am experienced php developer and I have everything setup for design/development/testing etc and I can develop locally on my machine using wamp. My question is, what should I be looking into for setting up a professional local development environment for developing web applications?
I have an Azure application that works perfectly on every one of my colleagues machines. On mine, the web application works, but not the azure project, which runs on the local development fabric.
I'm getting a 403 error, which causes a blank page in Chrome. The application_start method gets fired and sets up the routes, but the actual MVC controller never gets called. Again, this works perfect if I run the web application directly. If I use that same azure project and deploy it online, it also works fine.
I've tried repairing visual studio, reinstalling Azure, rebooting, re-fetching source, you name it.
We currently have a problem whereby on our stage servers, links that exist on certain pages have a full url instead of a relative path, for example they may be on http://stage.host.com/app/webpage1.aspx, and a link may exist to http://www.host.com/app/webpage2.aspx instead of http://stage.host.com/app/webpage2.aspxTo try and solve this problem we added a response filter to strip out the host name for anchor tags, so that they become relative. Although this works well for most situations, there are still some issues where users redirect to full links with server side code e.g. Response.Redirect.I wanted to get your guys ideas about the best way to tackle this problem,
I have a bigger ASP.NET based webapplication, which is structured into subwebs (as described on [URL]How can I share user specific information (user credentials, other informations) between these subwebs? The point is that the subwebs have all their own virtual directories and therefore different sessions. Are there other possibilities besides cookies to have a shared (user/browser session based) memory?
I need to set up a developement environment using msbuild and continuious integration, NUnit etc. I am quite new to this kind of thing as it is normally already set up in most environments ive worked in. I am quite short of time as well and dont have have the time to read huge volumes in order to get an understanding (developement starts Monday next week) so need to get this up and running asap in the shortest possible time. Does anyone have a working sample I can utilise or a short tutorial that breaks this process down?
I have just ported my VS2008 development environment to a new computer running Windows 7. One roadblock I'm having is that when I edit machine.config in VS2008, I cannot save it back to its location - I get an error saying Access Denied. I am logged in as Administrator and have tried to set myself up as owner but the crazy security rules in Windows 7 are frustrating this operation. (I could do this on my previous system - VS2008 running XP.) I set the Administrators permissions to Full Control and made this file's owner Administrators (vs the previous SYSTEM)
I'm using Visual Studio 2010 and working on an ASP.NET 4.0 web application. At the moment, a co-worker and I are tweaking CSS, which means constantly changing and saving CSS files and then refreshing the running page in a web browser.Every few saves, the application restarts, causing a considerable delay while we wait for the app to start up, log in again, and return to the page we were working on. In an IIS production environment a CSS file wouldn't go through the ASP.NET ISAPI, but apparently when running with VS2010 and the developent web server this doesn't matter... or something.
My overall goal is just to get the logged on users information for an Intranet site I'm developing without them providing their login (since they are already logged into their computer). So far I just get 401.1 errors and it keeps asking for my login/password. Even though I provide my login/password, it still won't let me in.
I've Enabled Windows Authentication from IIS > Sites > Default Web Site, added this to my web.config:
I made an aspx site with .net 4.0 framework through visual studio and it worked perfectly in the development environment but when I upload it to the server and try to run it I get this error: Server Error in '/' Application. Runtime Error Does anyone have an idea on how to fix this?
I am trying to implement URL rewriting technique in my Web application.I have found some articles on net 2 rewrite URL. But i m not able to understand. tell me any API or DLL which will take care of all url rewriting techniques in my Web applications.
I have heard something abt UrlRewriter.ddl . But i have not used it yet. provide me the easiest way to do that. If any sample application is there then it will be better ti understand
We have a largely asp.net web form team (With some Oracle developers thrown in).
Question 1:
Is it a good idea to start using asp.net MVC which will mean redevelopment of a number of standard controls for not much benefit.
Question 2:
Is it a good idea to hire developers where there most recent skills are with asp.net MVC?
I doubt there is any benefit adopting MVC now, given the 100+ applications in this suite of products, and the maintenance/rework this will cause. Given this, is there any particular reason to hire MVC developers, as they won't be hitting the ground running, which is what I need now.
I am planning to develop a social networking website for student of a particular university with following facilities.
Forum, Blog, Creating profile, creating groups , Adding Friends, managing groups, dating, chatting etc.
Now if I start developing it from scratch, this will take a lot of time..
I couldnt find any CMS which can in developing social networking website.
Additionally, I would like the website to have my own custom design. Also it should have support for AJAX, SEO and integrating third party applications.
How do you know what is better to use for writing new programs? We are now using Access 2007 frontend with an SQL backend and we are going to VB.Net, what would be our next logical step?
I'm currently using URL Rewriting, but I recently stumbled upon this link on Rerouting, and it looks like it's quite simple yet powerful, and easier to implement than URL Rewriting, a "downside" probably is that configurations are not sitting on a web.config file but rather on the code itself, but I was wondering about the differences, and advantages of using one over the other. Having read some resources about routing, I can see the differences, and now I reformulate my question:
Is it worth it to move from URL Rewriting to Routing? Are there any IIS-specific configurations that should be made? Is it recommended to use it on a ASP.NET WebForms Application, or is it oriented to other kind of projects?
I am using the 404 error page and a base class to serve all of my pages.
I have a url /restaurants/?page=2 which displays correctly. The restaurants folder does not physically exists.
I have a paging system, that I want to have the URLs /restaurants/default2.asp as this matches my old asp system.
My Question is can I have a rewrite rule for /restaurants/default2.asp to /restaurants/?page=2 though the restaurants folder does not exist and is served by the 404 error page.
I cant get it to work, and am wondering if the redirect works after the 404 error page is checked
