[RESOLVED] Question about localhost:nnnn vs localhost

Quote:

---

Originally Posted by szlamany

you can only use 1609 if that's the port that VS started the ASP.Net dev environment under -

---

Yes, I had verified that.

Quote:

---

Originally Posted by szlamany

create an IMAGES folder up or down from the folder it's looking for and see if you can at least get the image to be found.

---

Yeah, that's what I was just thinking of trying.

Creating an IMAGES folder was an epic failure, onto the net thing... (Woops, meant "next thing" - Freudian slip???)

What troubled me was I got this project from my coworker and when she loaded it, it used IIS but when I loaded it, it used Cassini. Odd. She sent me her sln file and I did a side-by-side text comparison and edited mine to match hers, most notably I changed this:
From: Project("{*** long numeric string ***}") = "XXX Web Enrollment", "D:\New Website Projects\XXX Web Enrollment", "{*** long numeric string ***}"
To: Project("{*** long numeric string ***}") = "XXX Web Enrollment", "http://localhost/XXX Web Enrollment", "{*** long numeric string ***}"

Now when I run, it opens up a browser window and does not start the ASP.NET development server and the URL is localhost without the port, BUT...something is wrong because I get an error that it is missing service.wsdl in App_WebReferences\ApplicationSecurity.

I believe you proved you have a SOLUTION difference - but I think your brute-force method of editing the SLN file is not a good idea.

You need to "select a browser service" from within the IDE so it can properly align that change...

Or someone really messed up a project creation.

Is this a WEB PROJECT vs WEB FOLDER kind of problem??

Going back to square one (that being getting the project and source files from a zip file on the network). Will let you know how it goes.

Well, this is such a disappointing resolution. It's working now, simply from me grabbing the project fresh from a zip file. But that was where I got it in the first place weeks ago, so why it's suddenly working beats me.

Here is the history. This project belonged to programmer A who worked in another department and was transitioning his project to our department. He put a zip file on a fileshare as a way of giving us the project (why we don't go to Source Control or TFS, I don't know). Programmer B worked with it to get it working (she "couldn't get it to run" but changed some web.config settings and created a VD in IIS, etc) and zipped it to another location for Programmer Me and Programmer C to get (never heard much from C). When I got it and ran it, it ran, but with the unresolved image and styling issue and running from ASP.NET Development Server instead of IIS. So today she tells me to get it from the zip file again, and all is miraculously working wonderfully. I am guessing she made some changes after she created the zip file that weren't propogated back in order for me to get them. Then she created the zip file again today. I can't really say what those changes were - perhaps, Steve, some of it was the changes I had made in an editor to the sln file which you said would be better off made in the IDE itself.

Thanks for all the help. Even though I didn't end up being the one to solve this and can't really say what did solve it, I think I learned a lot.

Quote:

---

Originally Posted by MMock

Going back to square one (that being getting the project and source files from a zip file on the network). Will let you know how it goes.

---

Really?!? Is there no source control repository being used? SVN? Git? TFS? Even VSS?

Quote:

---

Originally Posted by MMock

Well, this is such a disappointing resolution. It's working now, simply from me grabbing the project fresh from a zip file. But that was where I got it in the first place weeks ago, so why it's suddenly working beats me.

Here is the history. This project belonged to programmer A who worked in another department and was transitioning his project to our department. He put a zip file on a fileshare as a way of giving us the project (why we don't go to Source Control or TFS, I don't know). Programmer B worked with it to get it working (she "couldn't get it to run" but changed some web.config settings and created a VD in IIS, etc) and zipped it to another location for Programmer Me and Programmer C to get (never heard much from C). When I got it and ran it, it ran, but with the unresolved image and styling issue and running from ASP.NET Development Server instead of IIS. So today she tells me to get it from the zip file again, and all is miraculously working wonderfully. I am guessing she made some changes after she created the zip file that weren't propogated back in order for me to get them. Then she created the zip file again today. I can't really say what those changes were - perhaps, Steve, some of it was the changes I had made in an editor to the sln file which you said would be better off made in the IDE itself.

Thanks for all the help. Even though I didn't end up being the one to solve this and can't really say what did solve it, I think I learned a lot.

---

If this isn't a great story on why to use Source Control, I don't know what would be :)

Glad to hear that you got it all sorted out though!

Gary

Oh, we use source control; what I said was we didn't go to it in this case. Meaning, the developer who was the owner of the project zipped it up as a means of delivering it to us. I had also said "why...I don't know", but this is not the first project that has been like that. It seems to be the preferred MO.

Quote:

---

Originally Posted by MMock

Oh, we use source control; what I said was we didn't go to it in this case. Meaning, the developer who was the owner of the project zipped it up as a means of delivering it to us. I had also said "why...I don't know", but this is not the first project that has been like that. It seems to be the preferred MO.

---

Yeah, I read all that after I had read and responded to post #44, before reading post #45. I should have gone back and edited it :)