Publishing a mvc 5 app using Folderprofile does not work after copying it to Windows Server host
up vote
0
down vote
favorite
When I publish my app to a windows server I get a weird problem. Seems like the app thinks it's still running on my local machine:
What am I doing wrong?
Publishing to azure works as intended.
[NullReferenceException: Object reference not set to an instance of an object.] TestApp.Controllers.HomeController.Index() in C:UsersMyUserNameSourceReposTestAppTestAppControllersHomeController.cs:17
asp.net-mvc
add a comment |
up vote
0
down vote
favorite
When I publish my app to a windows server I get a weird problem. Seems like the app thinks it's still running on my local machine:
What am I doing wrong?
Publishing to azure works as intended.
[NullReferenceException: Object reference not set to an instance of an object.] TestApp.Controllers.HomeController.Index() in C:UsersMyUserNameSourceReposTestAppTestAppControllersHomeController.cs:17
asp.net-mvc
1
sometimes you see this if the error is in a compiled DLL, and it was compiled on your local machine, so the stack trace shows the code path as it was when it was compiled. Are you just asking us about why the path looks like that, or are you really asking how to fix the null reference exception? It's not clear. We can't fix the exception without a lot more detail, obviously.
– ADyson
Nov 9 at 12:54
I was asking about why the local path was in there... How do I proceed in figuring out what's wrong since it works on my local machine and azure?
– Supernalle
Nov 9 at 14:31
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I publish my app to a windows server I get a weird problem. Seems like the app thinks it's still running on my local machine:
What am I doing wrong?
Publishing to azure works as intended.
[NullReferenceException: Object reference not set to an instance of an object.] TestApp.Controllers.HomeController.Index() in C:UsersMyUserNameSourceReposTestAppTestAppControllersHomeController.cs:17
asp.net-mvc
When I publish my app to a windows server I get a weird problem. Seems like the app thinks it's still running on my local machine:
What am I doing wrong?
Publishing to azure works as intended.
[NullReferenceException: Object reference not set to an instance of an object.] TestApp.Controllers.HomeController.Index() in C:UsersMyUserNameSourceReposTestAppTestAppControllersHomeController.cs:17
asp.net-mvc
asp.net-mvc
asked Nov 9 at 12:49
Supernalle
83
83
1
sometimes you see this if the error is in a compiled DLL, and it was compiled on your local machine, so the stack trace shows the code path as it was when it was compiled. Are you just asking us about why the path looks like that, or are you really asking how to fix the null reference exception? It's not clear. We can't fix the exception without a lot more detail, obviously.
– ADyson
Nov 9 at 12:54
I was asking about why the local path was in there... How do I proceed in figuring out what's wrong since it works on my local machine and azure?
– Supernalle
Nov 9 at 14:31
add a comment |
1
sometimes you see this if the error is in a compiled DLL, and it was compiled on your local machine, so the stack trace shows the code path as it was when it was compiled. Are you just asking us about why the path looks like that, or are you really asking how to fix the null reference exception? It's not clear. We can't fix the exception without a lot more detail, obviously.
– ADyson
Nov 9 at 12:54
I was asking about why the local path was in there... How do I proceed in figuring out what's wrong since it works on my local machine and azure?
– Supernalle
Nov 9 at 14:31
1
1
sometimes you see this if the error is in a compiled DLL, and it was compiled on your local machine, so the stack trace shows the code path as it was when it was compiled. Are you just asking us about why the path looks like that, or are you really asking how to fix the null reference exception? It's not clear. We can't fix the exception without a lot more detail, obviously.
– ADyson
Nov 9 at 12:54
sometimes you see this if the error is in a compiled DLL, and it was compiled on your local machine, so the stack trace shows the code path as it was when it was compiled. Are you just asking us about why the path looks like that, or are you really asking how to fix the null reference exception? It's not clear. We can't fix the exception without a lot more detail, obviously.
– ADyson
Nov 9 at 12:54
I was asking about why the local path was in there... How do I proceed in figuring out what's wrong since it works on my local machine and azure?
– Supernalle
Nov 9 at 14:31
I was asking about why the local path was in there... How do I proceed in figuring out what's wrong since it works on my local machine and azure?
– Supernalle
Nov 9 at 14:31
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53226023%2fpublishing-a-mvc-5-app-using-folderprofile-does-not-work-after-copying-it-to-win%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
sometimes you see this if the error is in a compiled DLL, and it was compiled on your local machine, so the stack trace shows the code path as it was when it was compiled. Are you just asking us about why the path looks like that, or are you really asking how to fix the null reference exception? It's not clear. We can't fix the exception without a lot more detail, obviously.
– ADyson
Nov 9 at 12:54
I was asking about why the local path was in there... How do I proceed in figuring out what's wrong since it works on my local machine and azure?
– Supernalle
Nov 9 at 14:31