current community

your communities

more stack exchange communities

Stack Exchange Inbox Reputation and Badges
tour help
Sign up ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.
up vote -3 down vote favorite

I'm not too experienced in the regard of configuring IIS/ASP.net. A client has asked me to extend the functionality of a custom web application I didn't develop. Unfortunately, they don't have the original Visual Studio project/source code. I'm trying to pull the application off of their production IIS server and configure it for development on my machine. I've already setup a new website instance in IIS on my machine and copied the code to it's directory. When I access it (http://localhost), I'm currently receiving a null reference in the application. Obviously, this is a pretty generic error the can be caused by a bug, but I feel it's related to IIS's configuration. I've made sure both sites are using the same .NET version and they are also both running in integrated pipeline mode. Any ideas on what else I should look into?

Production server: Server 2008 R2 (64bit), IIS 7.5 Development machine: Win7 (64bit), IIS 7.5

share|improve this question

closed as too broad by MichaelT, gnat, Bart van Ingen Schenau, GlenH7, Robert Harvey Mar 31 '14 at 17:08

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.
    
This is a pretty broad topic. –  Adam Zuckerman Mar 28 '14 at 1:38
3  
This question appears to be off-topic because it is about an implementation issue. It potentially would be on-topic at another SE site but does not provide enough information for a meaningful answer to be written. –  GlenH7 Mar 28 '14 at 10:45

1 Answer 1

up vote -3 down vote accepted

I agree this was a broad question - if it's worth anything in the future, check the connection strings too. I forgot ASP.net would be connecting to most of these datasources on startup. This/bad error handling was the issue in my case.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.