469,625 Members | 1,155 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,625 developers. It's quick & easy.

How do i move a project from a local development pc to a server ?

Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro computer
which uses IIS/localhost, to another xp pro computer that is on a Windows
2003 server domain. I want to be able to use the Windows 2003 server IIS
instead of localhost.

I'm not trying to deploy the project for end user use. I'm still developing
and want to now continue development on new xp that is part of the Windows
2003 server.

When i try to open the project on the xp (which does not have IIS running
locally)connected to the Windows 2003, i get an error that says it can't
find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony
Oct 5 '06 #1
29 2479
--FTP the files over to the webhost.

--attach the database if necessary

"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message news:%2****************@TK2MSFTNGP05.phx.gbl...
Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro computer which uses IIS/localhost, to another xp pro computer
that is on a Windows 2003 server domain. I want to be able to use the Windows 2003 server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still developing and want to now continue development on new xp that
is part of the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running locally)connected to the Windows 2003, i get an error
that says it can't find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony

Oct 5 '06 #2
Thanks Jon. I'll give it a try.

"Jon Paal" <Jon[ nospam ]Paal @ everywhere dot comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
--FTP the files over to the webhost.

--attach the database if necessary

"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro
computer which uses IIS/localhost, to another xp pro computer that is on
a Windows 2003 server domain. I want to be able to use the Windows 2003
server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still
developing and want to now continue development on new xp that is part of
the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running
locally)connected to the Windows 2003, i get an error that says it can't
find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony


Oct 6 '06 #3
Hi,

I don't think you can do it like this. You are saying you want to move
your project from a stand-alone XP box _with_ IIS to a domain XP box
_without_ IIS, and expect it to still work? No.

You are then suggesting you might actually develop it directly on the
server?? Absolutely not!

You'd usually have to ask the domain admin the correct procedure to use
on their specific network. They will set it up for you. In general (with
VS2003) you'd need an XP box on the domain which _does_ have IIS
installed, then you'd develop on that box and publish to the 2003 server
when ready.

With VS2005 it's a LOT easier because you don't need to run IIS at all
on the development boxes.

Tony Girgenti wrote:
Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro computer
which uses IIS/localhost, to another xp pro computer that is on a Windows
2003 server domain. I want to be able to use the Windows 2003 server IIS
instead of localhost.

I'm not trying to deploy the project for end user use. I'm still developing
and want to now continue development on new xp that is part of the Windows
2003 server.

When i try to open the project on the xp (which does not have IIS running
locally)connected to the Windows 2003, i get an error that says it can't
find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony


--
Gerry Hickman (London UK)
Oct 8 '06 #4
Hello Gerry.

Thanks for your reply. Can you look at this and tell me if i interpreted
step 4 in the wrong way:
http://msdn.microsoft.com/library/de...anagedcode.asp

I am the administrator for the 2003 server. I don't necessarily want to
*move* the solution, i just want the ability to develop my solution at
home(where i am using IIS 5.1) or at the office (where i have a real live
server).

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:eP****************@TK2MSFTNGP02.phx.gbl...
Hi,

I don't think you can do it like this. You are saying you want to move
your project from a stand-alone XP box _with_ IIS to a domain XP box
_without_ IIS, and expect it to still work? No.

You are then suggesting you might actually develop it directly on the
server?? Absolutely not!

You'd usually have to ask the domain admin the correct procedure to use on
their specific network. They will set it up for you. In general (with
VS2003) you'd need an XP box on the domain which _does_ have IIS
installed, then you'd develop on that box and publish to the 2003 server
when ready.

With VS2005 it's a LOT easier because you don't need to run IIS at all on
the development boxes.

Tony Girgenti wrote:
>Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro
computer which uses IIS/localhost, to another xp pro computer that is on
a Windows 2003 server domain. I want to be able to use the Windows 2003
server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still
developing and want to now continue development on new xp that is part of
the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running
locally)connected to the Windows 2003, i get an error that says it can't
find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony


--
Gerry Hickman (London UK)

Oct 10 '06 #5
Hi,

I think there's two separate questions here. You also didn't make it
clear you were talking about a "web service" before. I thought you were
talking about a web project (web app).

Q1. How can I develop using IIS at home and at work with VS2003
Q2. How do I deploy a web service to a production server

Is that right?

or, are you saying you never want to visit the office, you want remote
debugging and ability to develop the whole thing on the live server from
a remote location (which will screw up the users who are trying to use it)

(the Step 4 you link to below glosses over the details)

There are lots of different answers to the above questions.

Tony Girgenti wrote:
Hello Gerry.

Thanks for your reply. Can you look at this and tell me if i interpreted
step 4 in the wrong way:
http://msdn.microsoft.com/library/de...anagedcode.asp

I am the administrator for the 2003 server. I don't necessarily want to
*move* the solution, i just want the ability to develop my solution at
home(where i am using IIS 5.1) or at the office (where i have a real live
server).

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:eP****************@TK2MSFTNGP02.phx.gbl...
>Hi,

I don't think you can do it like this. You are saying you want to move
your project from a stand-alone XP box _with_ IIS to a domain XP box
_without_ IIS, and expect it to still work? No.

You are then suggesting you might actually develop it directly on the
server?? Absolutely not!

You'd usually have to ask the domain admin the correct procedure to use on
their specific network. They will set it up for you. In general (with
VS2003) you'd need an XP box on the domain which _does_ have IIS
installed, then you'd develop on that box and publish to the 2003 server
when ready.

With VS2005 it's a LOT easier because you don't need to run IIS at all on
the development boxes.

Tony Girgenti wrote:
>>Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro
computer which uses IIS/localhost, to another xp pro computer that is on
a Windows 2003 server domain. I want to be able to use the Windows 2003
server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still
developing and want to now continue development on new xp that is part of
the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running
locally)connected to the Windows 2003, i get an error that says it can't
find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony

--
Gerry Hickman (London UK)


--
Gerry Hickman (London UK)
Oct 12 '06 #6
Hello Gerry.

Here is what i have at home:
I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer of a
web service. It is not a web service itself that other clients can consume.

At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0 on a
SBS2003 server computer with multiple workstations logged into the domain.
All ws's are XP Pro SP2. One of them is mine. I can log onto the domain.
The ws i have does not have IIS on it.

Can i take my project to the office and install IIS5.1 on my XP Pro computer
there and install whatever else is needed to develop the project the same
way i am doing it at home ? Absolutely. I am sure that i can do that.

I just thought it would be nice to use the server that i have at the office,
since it is a real live server and not just IIS5.1 localhost web service.
If you think this cannot be done, i will certainly do what i just explained
in the previous paragraph. Also, i thought it would be good to do because,
when i am finally done with the web consuming project, it will be installed
on a real live 2003 server also.

I don't need to remote in to do anything, although i probably will once i
have this set up at the office.

I'm sure there a lot of different ways to do it and if you have anyway to do
it, that is what i am looking for.

Hoping that you have an answer.

Thanks for all of your help with this.

Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
Hi,

I think there's two separate questions here. You also didn't make it clear
you were talking about a "web service" before. I thought you were talking
about a web project (web app).

Q1. How can I develop using IIS at home and at work with VS2003
Q2. How do I deploy a web service to a production server

Is that right?

or, are you saying you never want to visit the office, you want remote
debugging and ability to develop the whole thing on the live server from a
remote location (which will screw up the users who are trying to use it)

(the Step 4 you link to below glosses over the details)

There are lots of different answers to the above questions.

Tony Girgenti wrote:
>Hello Gerry.

Thanks for your reply. Can you look at this and tell me if i interpreted
step 4 in the wrong way:
http://msdn.microsoft.com/library/de...anagedcode.asp

I am the administrator for the 2003 server. I don't necessarily want to
*move* the solution, i just want the ability to develop my solution at
home(where i am using IIS 5.1) or at the office (where i have a real live
server).

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:eP****************@TK2MSFTNGP02.phx.gbl...
>>Hi,

I don't think you can do it like this. You are saying you want to move
your project from a stand-alone XP box _with_ IIS to a domain XP box
_without_ IIS, and expect it to still work? No.

You are then suggesting you might actually develop it directly on the
server?? Absolutely not!

You'd usually have to ask the domain admin the correct procedure to use
on their specific network. They will set it up for you. In general (with
VS2003) you'd need an XP box on the domain which _does_ have IIS
installed, then you'd develop on that box and publish to the 2003 server
when ready.

With VS2005 it's a LOT easier because you don't need to run IIS at all
on the development boxes.

Tony Girgenti wrote:
Hello.

I'm developing and testing a web application using VS.NET 2003, VB,
.NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro
computer which uses IIS/localhost, to another xp pro computer that is
on a Windows 2003 server domain. I want to be able to use the Windows
2003 server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still
developing and want to now continue development on new xp that is part
of the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS
running locally)connected to the Windows 2003, i get an error that says
it can't find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony

--
Gerry Hickman (London UK)



--
Gerry Hickman (London UK)

Oct 13 '06 #7
Hi Tony,
I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer of a
web service. It is not a web service itself that other clients can consume.
OK, that's clear now.
At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0 on a
SBS2003 server computer with multiple workstations logged into the domain.
All ws's are XP Pro SP2. One of them is mine. I can log onto the domain.
The ws i have does not have IIS on it.
Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.
Can i take my project to the office and install IIS5.1 on my XP Pro computer
there and install whatever else is needed to develop the project the same
way i am doing it at home ? Absolutely. I am sure that i can do that.
Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under
Microsoft's o/s. Again, this is improved in VS2005 as you don't need IIS
on the client.
I just thought it would be nice to use the server that i have at the office,
since it is a real live server and not just IIS5.1 localhost web service.
If you think this cannot be done,
It could be "done", but the proper way to do it is to develop on a
client computer, then publish it to the server when it's fully debugged
and tested. You can then work on new versions without affecting the live
server.

--
Gerry Hickman (London UK)
Oct 13 '06 #8
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:uj**************@TK2MSFTNGP05.phx.gbl...
At he office i have VS.NET 2003 on a SBS2003 server computer
No way!!! You've installed Visual Studio.NET on your server???
Oct 13 '06 #9
Hello Gerry.
>Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.<<

What i did was just put the cd's on the server and installed it locally on
my pc. According to Microsoft, that is allowed.

But i don't see what that has to do with the question i am asking. I am the
Administrator at my office and IIS 6.0 is already set up on the 2003 server.
When i take my project to my office and put it on my pc at the office and
try to open it with VS.NET 2003, it gives a message saying that it can't
find localhost.

How do i take this project to my office and continue to develop it on my pc
while i am at the office ? Instead of just working on it at home, i want to
be able to work on it while i am at the office.

Thanks
Tony
"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uH**************@TK2MSFTNGP04.phx.gbl...
Hi Tony,
>I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer of
a web service. It is not a web service itself that other clients can
consume.

OK, that's clear now.
>At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0 on
a SBS2003 server computer with multiple workstations logged into the
domain. All ws's are XP Pro SP2. One of them is mine. I can log onto
the domain. The ws i have does not have IIS on it.

Yikes, you installed VS.NET 2003 to a live server? That's very bad! Breaks
every rule of client/server computing.
>Can i take my project to the office and install IIS5.1 on my XP Pro
computer there and install whatever else is needed to develop the project
the same way i am doing it at home ? Absolutely. I am sure that i can
do that.

Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under Microsoft's
o/s. Again, this is improved in VS2005 as you don't need IIS on the
client.
>I just thought it would be nice to use the server that i have at the
office, since it is a real live server and not just IIS5.1 localhost web
service. If you think this cannot be done,

It could be "done", but the proper way to do it is to develop on a client
computer, then publish it to the server when it's fully debugged and
tested. You can then work on new versions without affecting the live
server.

--
Gerry Hickman (London UK)

Oct 13 '06 #10
Hello mark.

I got this from a readme on the VS.NET2003 cd's:

2. System Requirements
The tables below list requirements for different installation options of
Visual Studio .NET 2003. The Notes identified here apply to both tables.

System Requirements for Installing Visual Studio .NET 2003

Visual Studio .NET 2003 (All Editions)
Processor 450 megahertz (MHz) Pentium II-class processor
600 MHz Pentium III-class processor recommended
Operating System Visual Studio .NET 2003 can be installed on any of
the following systems:

a.. Microsoft Windows Server 2003
b.. Windows XP Professional
c.. Windows XP Home Edition1
d.. Windows 2000 Professional (Service Pack 3 or later required)6
e.. Windows 2000 Server (Service Pack 3 or later required)6
Applications can be deployed to the following systems2, 3:

a.. Microsoft Windows Server 2003
b.. Windows XP Professional
c.. Windows XP Home Edition
d.. Windows 2000 (Service Pack 3 or later recommended)
e.. Windows Millennium Edition (Windows Me)
f.. Windows 98
g.. Microsoft Windows NT 4.0 (Service Pack 6a required)
"Mark Rae" <ma**@markNOSPAMrae.comwrote in message
news:OG**************@TK2MSFTNGP02.phx.gbl...
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:uj**************@TK2MSFTNGP05.phx.gbl...
>At he office i have VS.NET 2003 on a SBS2003 server computer

No way!!! You've installed Visual Studio.NET on your server???

Oct 13 '06 #11
>>What i did was just put the cd's on the server and installed it locally on
>>my pc. According to Microsoft, that is allowed.
Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
dropping in and I couldn't actuallly help you as I am also actually
looking for answer to my question. Good luck :)

Oct 14 '06 #12
Uhhh. What's so funny ?

<wa**********@gmail.comwrote in message
news:11********************@i3g2000cwc.googlegroup s.com...
>>>What i did was just put the cd's on the server and installed it locally
on
my pc. According to Microsoft, that is allowed.

Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
dropping in and I couldn't actuallly help you as I am also actually
looking for answer to my question. Good luck :)

Oct 14 '06 #13
So i guess nobody has an answer for this.

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uH**************@TK2MSFTNGP04.phx.gbl...
Hi Tony,
>I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer of
a web service. It is not a web service itself that other clients can
consume.

OK, that's clear now.
>At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0 on
a SBS2003 server computer with multiple workstations logged into the
domain. All ws's are XP Pro SP2. One of them is mine. I can log onto
the domain. The ws i have does not have IIS on it.

Yikes, you installed VS.NET 2003 to a live server? That's very bad! Breaks
every rule of client/server computing.
>Can i take my project to the office and install IIS5.1 on my XP Pro
computer there and install whatever else is needed to develop the project
the same way i am doing it at home ? Absolutely. I am sure that i can
do that.

Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under Microsoft's
o/s. Again, this is improved in VS2005 as you don't need IIS on the
client.
>I just thought it would be nice to use the server that i have at the
office, since it is a real live server and not just IIS5.1 localhost web
service. If you think this cannot be done,

It could be "done", but the proper way to do it is to develop on a client
computer, then publish it to the server when it's fully debugged and
tested. You can then work on new versions without affecting the live
server.

--
Gerry Hickman (London UK)

Oct 16 '06 #14
Hi Tony,

I'll quickly answer the part about installing VS.NET IDE on a server.

DON'T DO IT.

Some components included with VS.NET 2003 are SUPPOSED to be installed
on a server, but that's a different story.

The system requirements are just requirements for the application to
run. They are not actually suggesting it's a viable development model
for the real world.

I could write a book on why it's a bad idea.

Tony Girgenti wrote:
Uhhh. What's so funny ?

<wa**********@gmail.comwrote in message
news:11********************@i3g2000cwc.googlegroup s.com...
>>>What i did was just put the cd's on the server and installed it locally
on
my pc. According to Microsoft, that is allowed.
Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
dropping in and I couldn't actuallly help you as I am also actually
looking for answer to my question. Good luck :)


--
Gerry Hickman (London UK)
Oct 17 '06 #15
Hi Tony,

I've already answered this below. See the part where I said "Yes, this
is the proper course of action..."

Tony Girgenti wrote:
Hello Gerry.
>>Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.<<

What i did was just put the cd's on the server and installed it locally on
my pc. According to Microsoft, that is allowed.

But i don't see what that has to do with the question i am asking. I am the
Administrator at my office and IIS 6.0 is already set up on the 2003 server.
When i take my project to my office and put it on my pc at the office and
try to open it with VS.NET 2003, it gives a message saying that it can't
find localhost.

How do i take this project to my office and continue to develop it on my pc
while i am at the office ? Instead of just working on it at home, i want to
be able to work on it while i am at the office.

Thanks
Tony
"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uH**************@TK2MSFTNGP04.phx.gbl...
>Hi Tony,
>>I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer of
a web service. It is not a web service itself that other clients can
consume.
OK, that's clear now.
>>At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0 on
a SBS2003 server computer with multiple workstations logged into the
domain. All ws's are XP Pro SP2. One of them is mine. I can log onto
the domain. The ws i have does not have IIS on it.
Yikes, you installed VS.NET 2003 to a live server? That's very bad! Breaks
every rule of client/server computing.
>>Can i take my project to the office and install IIS5.1 on my XP Pro
computer there and install whatever else is needed to develop the project
the same way i am doing it at home ? Absolutely. I am sure that i can
do that.
Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under Microsoft's
o/s. Again, this is improved in VS2005 as you don't need IIS on the
client.
>>I just thought it would be nice to use the server that i have at the
office, since it is a real live server and not just IIS5.1 localhost web
service. If you think this cannot be done,
It could be "done", but the proper way to do it is to develop on a client
computer, then publish it to the server when it's fully debugged and
tested. You can then work on new versions without affecting the live
server.

--
Gerry Hickman (London UK)


--
Gerry Hickman (London UK)
Oct 17 '06 #16
Hello Gerry.
>>Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under
Microsoft's o/s. Again, this is improved in VS2005 as you don't need IIS
on the client.
I don't see where this helps me resolve the problem of it telling me that it
can't find the server because it is looking for localhost.

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uU**************@TK2MSFTNGP02.phx.gbl...
Hi Tony,

I've already answered this below. See the part where I said "Yes, this is
the proper course of action..."

Tony Girgenti wrote:
>Hello Gerry.
>>>Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.<<

What i did was just put the cd's on the server and installed it locally
on my pc. According to Microsoft, that is allowed.

But i don't see what that has to do with the question i am asking. I am
the Administrator at my office and IIS 6.0 is already set up on the 2003
server. When i take my project to my office and put it on my pc at the
office and try to open it with VS.NET 2003, it gives a message saying
that it can't find localhost.

How do i take this project to my office and continue to develop it on my
pc while i am at the office ? Instead of just working on it at home, i
want to be able to work on it while i am at the office.

Thanks
Tony
"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uH**************@TK2MSFTNGP04.phx.gbl...
>>Hi Tony,

I'm developing and testing a web application using VS.NET 2003, VB,
.NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer
of a web service. It is not a web service itself that other clients
can consume.
OK, that's clear now.

At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0
on a SBS2003 server computer with multiple workstations logged into the
domain. All ws's are XP Pro SP2. One of them is mine. I can log onto
the domain. The ws i have does not have IIS on it.
Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.

Can i take my project to the office and install IIS5.1 on my XP Pro
computer there and install whatever else is needed to develop the
project the same way i am doing it at home ? Absolutely. I am sure
that i can do that.
Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under
Microsoft's o/s. Again, this is improved in VS2005 as you don't need IIS
on the client.

I just thought it would be nice to use the server that i have at the
office, since it is a real live server and not just IIS5.1 localhost
web service. If you think this cannot be done,
It could be "done", but the proper way to do it is to develop on a
client computer, then publish it to the server when it's fully debugged
and tested. You can then work on new versions without affecting the live
server.

--
Gerry Hickman (London UK)



--
Gerry Hickman (London UK)

Oct 18 '06 #17
Hello Gerry.

You keep telling me not to do this, but you don't say why. Are you telling
me that because you think it is illegal or do you know of a problem/s that
can occur by doing it ?

I know you said you could write a book, but could you give me just one
reason that i should not do it ?

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
Hi Tony,

I'll quickly answer the part about installing VS.NET IDE on a server.

DON'T DO IT.

Some components included with VS.NET 2003 are SUPPOSED to be installed on
a server, but that's a different story.

The system requirements are just requirements for the application to run.
They are not actually suggesting it's a viable development model for the
real world.

I could write a book on why it's a bad idea.

Tony Girgenti wrote:
>Uhhh. What's so funny ?

<wa**********@gmail.comwrote in message
news:11********************@i3g2000cwc.googlegrou ps.com...
>>>>What i did was just put the cd's on the server and installed it
locally on
my pc. According to Microsoft, that is allowed.
Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
dropping in and I couldn't actuallly help you as I am also actually
looking for answer to my question. Good luck :)



--
Gerry Hickman (London UK)

Oct 18 '06 #18
Hi Tony,

Here's the exact text of the question and answer again (for the 3rd time)

You wrote:
Can i take my project to the office and install IIS5.1 on my XP Pro
>>computer there and install whatever else is needed to develop the
project the same way i am doing it at home ? Absolutely. I am
sure
>>that i can do that.
I wrote:
>>Yes. This is the proper course of action.
Tony Girgenti wrote:
Hello Gerry.
>>>Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under
Microsoft's o/s. Again, this is improved in VS2005 as you don't need IIS
on the client.

I don't see where this helps me resolve the problem of it telling me that it
can't find the server because it is looking for localhost.

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uU**************@TK2MSFTNGP02.phx.gbl...
>Hi Tony,

I've already answered this below. See the part where I said "Yes, this is
the proper course of action..."

Tony Girgenti wrote:
>>Hello Gerry.

Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.<<

What i did was just put the cd's on the server and installed it locally
on my pc. According to Microsoft, that is allowed.

But i don't see what that has to do with the question i am asking. I am
the Administrator at my office and IIS 6.0 is already set up on the 2003
server. When i take my project to my office and put it on my pc at the
office and try to open it with VS.NET 2003, it gives a message saying
that it can't find localhost.

How do i take this project to my office and continue to develop it on my
pc while i am at the office ? Instead of just working on it at home, i
want to be able to work on it while i am at the office.

Thanks
Tony
"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uH**************@TK2MSFTNGP04.phx.gbl...
Hi Tony,

I'm developing and testing a web application using VS.NET 2003, VB,
.NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form. The application is a client/consumer
of a web service. It is not a web service itself that other clients
can consume.
OK, that's clear now.

At he office i have:
VS.NET 2003, VB, .NET Framework 1.1.4322, ASP.NET 1.1.4322 and IIS6.0
on a SBS2003 server computer with multiple workstations logged into the
domain. All ws's are XP Pro SP2. One of them is mine. I can log onto
the domain. The ws i have does not have IIS on it.
Yikes, you installed VS.NET 2003 to a live server? That's very bad!
Breaks every rule of client/server computing.

Can i take my project to the office and install IIS5.1 on my XP Pro
computer there and install whatever else is needed to develop the
project the same way i am doing it at home ? Absolutely. I am sure
that i can do that.
Yes. This is the proper course of action. Ask your Network Administrator
to help you configure IIS to exactly match your home system (or visa
versa) and also to set it up so it can work without logging is as an
Administrator, as this would be a serious security risk under
Microsoft's o/s. Again, this is improved in VS2005 as you don't need IIS
on the client.

I just thought it would be nice to use the server that i have at the
office, since it is a real live server and not just IIS5.1 localhost
web service. If you think this cannot be done,
It could be "done", but the proper way to do it is to develop on a
client computer, then publish it to the server when it's fully debugged
and tested. You can then work on new versions without affecting the live
server.

--
Gerry Hickman (London UK)

--
Gerry Hickman (London UK)


--
Gerry Hickman (London UK)
Oct 19 '06 #19
Hi Tony,

No, I'm not going to write a book (right now) on

1. The basics of client/server computing
2. The pros and cons of different development models in the context of
team working, source control, remote debugging, and remote access over
standards compliant protocols.
3. The low-level details of how security tokens are passed around modern
networks and how IIS determines which process runs with which token.
4. Good security practice on Windows networks and how Vista will affect
this.

But, feel free to ignore the advice if you don't like it, and then you
can write your own book in two years time!

Tony Girgenti wrote:
Hello Gerry.

You keep telling me not to do this, but you don't say why. Are you telling
me that because you think it is illegal or do you know of a problem/s that
can occur by doing it ?

I know you said you could write a book, but could you give me just one
reason that i should not do it ?

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>Hi Tony,

I'll quickly answer the part about installing VS.NET IDE on a server.

DON'T DO IT.

Some components included with VS.NET 2003 are SUPPOSED to be installed on
a server, but that's a different story.

The system requirements are just requirements for the application to run.
They are not actually suggesting it's a viable development model for the
real world.

I could write a book on why it's a bad idea.

Tony Girgenti wrote:
>>Uhhh. What's so funny ?

<wa**********@gmail.comwrote in message
news:11********************@i3g2000cwc.googlegro ups.com...
>What i did was just put the cd's on the server and installed it
>locally on
>my pc. According to Microsoft, that is allowed.
Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
dropping in and I couldn't actuallly help you as I am also actually
looking for answer to my question. Good luck :)


--
Gerry Hickman (London UK)


--
Gerry Hickman (London UK)
Oct 19 '06 #20
Hello Gerry.

I sense from this reply and your other one that you are perturbed about
something. It is not my intention to do so. If i have offended you in any
way, i would like to apologize for that.

I'm i am not ignoring your advice, I just don't see how my question of "how
do i move a VS.NET 2003 project from one standalone computer to a network
environment, when i attempt it, it says that it can't find 'localhost'" is
answered by your replies.

I'm not asking if it is OK to install VS.NET 2003 on my server or how to
configure IIS. I just need to know how to keep it from telling me that it
can't find localhost possibly by changing my program before i take it to my
office. I don't know the answer.

Again, I am sorry if you think that i am ignoring your advice. I post in
these forums for the knowledge and knowhow of the experts that monitor them
and in this case, i am simply looking for an answer to my specific problem.
I thought that someone with your apparent knowledge and expertise would be
able to tell me what to do.

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Hi Tony,

No, I'm not going to write a book (right now) on

1. The basics of client/server computing
2. The pros and cons of different development models in the context of
team working, source control, remote debugging, and remote access over
standards compliant protocols.
3. The low-level details of how security tokens are passed around modern
networks and how IIS determines which process runs with which token.
4. Good security practice on Windows networks and how Vista will affect
this.

But, feel free to ignore the advice if you don't like it, and then you can
write your own book in two years time!

Tony Girgenti wrote:
>Hello Gerry.

You keep telling me not to do this, but you don't say why. Are you
telling me that because you think it is illegal or do you know of a
problem/s that can occur by doing it ?

I know you said you could write a book, but could you give me just one
reason that i should not do it ?

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>>Hi Tony,

I'll quickly answer the part about installing VS.NET IDE on a server.

DON'T DO IT.

Some components included with VS.NET 2003 are SUPPOSED to be installed
on a server, but that's a different story.

The system requirements are just requirements for the application to
run. They are not actually suggesting it's a viable development model
for the real world.

I could write a book on why it's a bad idea.

Tony Girgenti wrote:
Uhhh. What's so funny ?

<wa**********@gmail.comwrote in message
news:11********************@i3g2000cwc.googlegr oups.com...
>>What i did was just put the cd's on the server and installed it
>>locally on
>>my pc. According to Microsoft, that is allowed.
Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
dropping in and I couldn't actuallly help you as I am also actually
looking for answer to my question. Good luck :)
>
--
Gerry Hickman (London UK)



--
Gerry Hickman (London UK)

Oct 19 '06 #21
re:
When i try to open the project on the xp (which does not have IIS running locally)
connected to the Windows 2003, i get an error that says it can't find localhost.
You *must* install IIS on that computer if you want to be able
to access a VS 2003 project copied to that computer.

First, install IIS on that XP Pro box.

Then, try to access the project.

When you open a Web project, the system opens it using the Web access method
(file share or FrontPage Server Extensions) last used for the project.

To open an existing Web project that is not part of source control

1. On the File menu, point to Open, and then choose Project From Web.
2. In the Open Project From Web dialog box, enter the URL of the Web server where the project is
located, and then click OK.
3. In the Open Project dialog box, double-click your Web project's folder.
4. Double-click the appropriate project file to open the project.

The Web project opens and its files are listed in Solution Explorer. If the project could not be
opened, an error message is shown that allows you to try another Web access method or to
work offline.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro computer which uses
IIS/localhost, to another xp pro computer that is on a Windows 2003 server domain. I want to be
able to use the Windows 2003 server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still developing and want to now
continue development on new xp that is part of the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running locally)connected to the
Windows 2003, i get an error that says it can't find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony


Oct 20 '06 #22
Hello Juan.

I don't want to install IIS on my XP Pro box.

However your information on opening a Project From Web gives me an idea to
try. I can probably open the Project From Web on the 2003 server.

I should probably pay more attention to the menu options.

Thanks,
Tony

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
re:
>When i try to open the project on the xp (which does not have IIS running
locally)
connected to the Windows 2003, i get an error that says it can't find
localhost.

You *must* install IIS on that computer if you want to be able
to access a VS 2003 project copied to that computer.

First, install IIS on that XP Pro box.

Then, try to access the project.

When you open a Web project, the system opens it using the Web access
method
(file share or FrontPage Server Extensions) last used for the project.

To open an existing Web project that is not part of source control

1. On the File menu, point to Open, and then choose Project From Web.
2. In the Open Project From Web dialog box, enter the URL of the Web
server where the project is
located, and then click OK.
3. In the Open Project dialog box, double-click your Web project's folder.
4. Double-click the appropriate project file to open the project.

The Web project opens and its files are listed in Solution Explorer. If
the project could not be
opened, an error message is shown that allows you to try another Web
access method or to
work offline.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro
computer which uses
IIS/localhost, to another xp pro computer that is on a Windows 2003
server domain. I want to be
able to use the Windows 2003 server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still
developing and want to now
continue development on new xp that is part of the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running
locally)connected to the
Windows 2003, i get an error that says it can't find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony



Oct 20 '06 #23
What made it a bit difficult to diagnose your problem is that you stated that :
When i try to open the project on the xp (which does not have IIS running locally)
That led me to believe that you wanted to open the project from that box.
I think you meant "open the project from the xp".

re:
I can probably open the Project From Web on the 2003 server.
Yup, you probably can.

re:
Thanks
You're quite welcome.
Good luck, and let us know how you do, OK ?


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:Oi***************@TK2MSFTNGP05.phx.gbl...
Hello Juan.

I don't want to install IIS on my XP Pro box.

However your information on opening a Project From Web gives me an idea to try. I can probably
open the Project From Web on the 2003 server.

I should probably pay more attention to the menu options.

Thanks,
Tony

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
>re:
>>When i try to open the project on the xp (which does not have IIS running locally)
connected to the Windows 2003, i get an error that says it can't find localhost.

You *must* install IIS on that computer if you want to be able
to access a VS 2003 project copied to that computer.

First, install IIS on that XP Pro box.

Then, try to access the project.

When you open a Web project, the system opens it using the Web access method
(file share or FrontPage Server Extensions) last used for the project.

To open an existing Web project that is not part of source control

1. On the File menu, point to Open, and then choose Project From Web.
2. In the Open Project From Web dialog box, enter the URL of the Web server where the project is
located, and then click OK.
3. In the Open Project dialog box, double-click your Web project's folder.
4. Double-click the appropriate project file to open the project.

The Web project opens and its files are listed in Solution Explorer. If the project could not be
opened, an error message is shown that allows you to try another Web access method or to
work offline.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>>Hello.

I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro computer which uses
IIS/localhost, to another xp pro computer that is on a Windows 2003 server domain. I want to be
able to use the Windows 2003 server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still developing and want to now
continue development on new xp that is part of the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS running locally)connected to
the
Windows 2003, i get an error that says it can't find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony




Oct 20 '06 #24
Hi Tony,
I sense from this reply and your other one that you are perturbed about
something.
Sorry, it's been a difficult week:)

There are two different questions here, both of which I've answered.

Q1, How can I use an XP client box with VS2003 and IIS 5.1 both at home
and at work, then publish to a production server.

Q2, Should I run VS2003 directly on a production server?

Can you try to keep each topic above separate, otherwise it's confusing.

Regarding Q2, I could write a book on "why", but I don't have time. Q1
has already been answered three times. If you'd set it up, you'd have
seen it's called localhost regardless of whether you're at home or at
work. The localhost hostname is assigned to the local computer (the one
you're sitting in front of) at IP address 127.0.0.1

If you develop on the local box, and use standards compliant HTTP as
opposed to Microsoft's non-standards based SMB and NetBIOS, you'll
notice the root of the local web server is called

http://localhost/

The production server is probably called something like

http://BigServer15/

It's fully canonical name would be something like

http://BigServer15.mycompany.com/

and there may be DNS records pointing to it (alises) simply called

http://mycomany.com/
I'm i am not ignoring your advice, I just don't see how my question of "how
do i move a VS.NET 2003 project from one standalone computer to a network
environment, when i attempt it, it says that it can't find 'localhost'" is
answered by your replies.

I'm not asking if it is OK to install VS.NET 2003 on my server or how to
configure IIS. I just need to know how to keep it from telling me that it
can't find localhost possibly by changing my program before i take it to my
office. I don't know the answer.

Again, I am sorry if you think that i am ignoring your advice. I post in
these forums for the knowledge and knowhow of the experts that monitor them
and in this case, i am simply looking for an answer to my specific problem.
I thought that someone with your apparent knowledge and expertise would be
able to tell me what to do.

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>Hi Tony,

No, I'm not going to write a book (right now) on

1. The basics of client/server computing
2. The pros and cons of different development models in the context of
team working, source control, remote debugging, and remote access over
standards compliant protocols.
3. The low-level details of how security tokens are passed around modern
networks and how IIS determines which process runs with which token.
4. Good security practice on Windows networks and how Vista will affect
this.

But, feel free to ignore the advice if you don't like it, and then you can
write your own book in two years time!

Tony Girgenti wrote:
>>Hello Gerry.

You keep telling me not to do this, but you don't say why. Are you
telling me that because you think it is illegal or do you know of a
problem/s that can occur by doing it ?

I know you said you could write a book, but could you give me just one
reason that i should not do it ?

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl.. .
Hi Tony,

I'll quickly answer the part about installing VS.NET IDE on a server.

DON'T DO IT.

Some components included with VS.NET 2003 are SUPPOSED to be installed
on a server, but that's a different story.

The system requirements are just requirements for the application to
run. They are not actually suggesting it's a viable development model
for the real world.

I could write a book on why it's a bad idea.

Tony Girgenti wrote:
Uhhh. What's so funny ?
>
<wa**********@gmail.comwrote in message
news:11********************@i3g2000cwc.googleg roups.com...
>>>What i did was just put the cd's on the server and installed it
>>>locally on
>>>my pc. According to Microsoft, that is allowed.
>Man, that is sweet , I couldn't resist a good laugh:)..I apologize for
>dropping in and I couldn't actuallly help you as I am also actually
>looking for answer to my question. Good luck :)
>>
--
Gerry Hickman (London UK)

--
Gerry Hickman (London UK)


--
Gerry Hickman (London UK)
Oct 20 '06 #25
Hello Gerry.

Sorry for the confusion. I should have made this clear from the beginning
and i apologize for that. I don't want to install IIS on the local
computer.

My server at the office is lakeside. When i am at home, i test by going to
http://localhost/CoyneTruckWebServices

When i go to my office, i want to be able to key in
http://lakeside/CoyneTruckWebServices

Using http://lakeside/CoyneTruckWebServices works at the office. I've
tried it with a small test program. I guess i could bring my source code to
the office, open that empty test program(which already runns from:
http://lakeside/CoyneTruckWebServices) , copy in my source code and aspx
file,from the source that i brought from home and i would essentially have
my project under development at the office. Instead of using a localhost
iis 5.1 at the office, i would be using lakeside's 6.0 iis.

I could do that. I just thought there would be an easier way to do that.

I'm sorry if i caused you to spend a lot of time on this problem, and your
replies indicate you did, simply because i did not explain it properly.

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
Hi Tony,
>I sense from this reply and your other one that you are perturbed about
something.

Sorry, it's been a difficult week:)

There are two different questions here, both of which I've answered.

Q1, How can I use an XP client box with VS2003 and IIS 5.1 both at home
and at work, then publish to a production server.

Q2, Should I run VS2003 directly on a production server?

Can you try to keep each topic above separate, otherwise it's confusing.

Regarding Q2, I could write a book on "why", but I don't have time. Q1 has
already been answered three times. If you'd set it up, you'd have seen
it's called localhost regardless of whether you're at home or at work. The
localhost hostname is assigned to the local computer (the one you're
sitting in front of) at IP address 127.0.0.1

If you develop on the local box, and use standards compliant HTTP as
opposed to Microsoft's non-standards based SMB and NetBIOS, you'll notice
the root of the local web server is called

http://localhost/

The production server is probably called something like

http://BigServer15/

It's fully canonical name would be something like

http://BigServer15.mycompany.com/

and there may be DNS records pointing to it (alises) simply called

http://mycomany.com/
>I'm i am not ignoring your advice, I just don't see how my question of
"how do i move a VS.NET 2003 project from one standalone computer to a
network environment, when i attempt it, it says that it can't find
'localhost'" is answered by your replies.

I'm not asking if it is OK to install VS.NET 2003 on my server or how to
configure IIS. I just need to know how to keep it from telling me that
it can't find localhost possibly by changing my program before i take it
to my office. I don't know the answer.

Again, I am sorry if you think that i am ignoring your advice. I post in
these forums for the knowledge and knowhow of the experts that monitor
them and in this case, i am simply looking for an answer to my specific
problem. I thought that someone with your apparent knowledge and
expertise would be able to tell me what to do.

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>>Hi Tony,

No, I'm not going to write a book (right now) on

1. The basics of client/server computing
2. The pros and cons of different development models in the context of
team working, source control, remote debugging, and remote access over
standards compliant protocols.
3. The low-level details of how security tokens are passed around modern
networks and how IIS determines which process runs with which token.
4. Good security practice on Windows networks and how Vista will affect
this.

But, feel free to ignore the advice if you don't like it, and then you
can write your own book in two years time!

Tony Girgenti wrote:
Hello Gerry.

You keep telling me not to do this, but you don't say why. Are you
telling me that because you think it is illegal or do you know of a
problem/s that can occur by doing it ?

I know you said you could write a book, but could you give me just one
reason that i should not do it ?

Thanks,
Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl. ..
Hi Tony,
>
I'll quickly answer the part about installing VS.NET IDE on a server.
>
DON'T DO IT.
>
Some components included with VS.NET 2003 are SUPPOSED to be installed
on a server, but that's a different story.
>
The system requirements are just requirements for the application to
run. They are not actually suggesting it's a viable development model
for the real world.
>
I could write a book on why it's a bad idea.
>
Tony Girgenti wrote:
>Uhhh. What's so funny ?
>>
><wa**********@gmail.comwrote in message
>news:11********************@i3g2000cwc.google groups.com...
>>>>What i did was just put the cd's on the server and installed it
>>>>locally on
>>>>my pc. According to Microsoft, that is allowed.
>>Man, that is sweet , I couldn't resist a good laugh:)..I apologize
>>for
>>dropping in and I couldn't actuallly help you as I am also actually
>>looking for answer to my question. Good luck :)
>>>
--
Gerry Hickman (London UK)
--
Gerry Hickman (London UK)



--
Gerry Hickman (London UK)

Oct 21 '06 #26
Tony Girgenti wrote:
Sorry for the confusion. I should have made this clear from the beginning
and i apologize for that. I don't want to install IIS on the local
computer.
Well installing IIS on the workstations is the correct solution for
VS2003, for VS2005 you don't need to worry about any of this.
My server at the office is lakeside. When i am at home, i test by going to
http://localhost/CoyneTruckWebServices

When i go to my office, i want to be able to key in
http://lakeside/CoyneTruckWebServices
Yes, it's quite easy to do this as long as you code everything relative
(e.g. HFEFs and FileSystem paths), however, this implies you're trying
to develop directly on the live server, but you haven't set up process
isolation and remote debugging, so it's not the correct way of doing it.

--
Gerry Hickman (London UK)
Oct 21 '06 #27
Hello Gerry.
>Yes, it's quite easy to do this as long as you code everything relative
(e.g. HFEFs and FileSystem paths), <<

I have no idea of what you mean by code everything relative and what HFEF
and FileSystem paths are.
>however, this implies you're trying
to develop directly on the live server, but you haven't set up process
isolation and remote debugging, so it's not the correct way of doing it. <<

I gather from this that you know how to do this, but you decide not to tell
me because you don't feel it is the correct way to develop this project and
you do not want to give me the incoorrect way of doing things. If that is
the case, i'm guessing, it's probably either against your better judgement
or something you feel is unethical.

Thanks for all of the help you have provided so far.

Tony

"Gerry Hickman" <ge********@newsgroup.nospamwrote in message
news:uz****************@TK2MSFTNGP04.phx.gbl...
Tony Girgenti wrote:
>Sorry for the confusion. I should have made this clear from the
beginning and i apologize for that. I don't want to install IIS on the
local computer.

Well installing IIS on the workstations is the correct solution for
VS2003, for VS2005 you don't need to worry about any of this.
>My server at the office is lakeside. When i am at home, i test by going
to http://localhost/CoyneTruckWebServices

When i go to my office, i want to be able to key in
http://lakeside/CoyneTruckWebServices

Yes, it's quite easy to do this as long as you code everything relative
(e.g. HFEFs and FileSystem paths), however, this implies you're trying to
develop directly on the live server, but you haven't set up process
isolation and remote debugging, so it's not the correct way of doing it.

--
Gerry Hickman (London UK)

Oct 21 '06 #28
Hello Juan.

When i try to open "Project From Web", i enter the server name in the url
box, select the web site i want to open and it gives this message:
"Documents in this folder are not available. The folder may have been moved
or deleted, or network problems may be preventing a connection to the
server."

Thanks,
Tony

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP06.phx.gbl...
What made it a bit difficult to diagnose your problem is that you stated
that :
>When i try to open the project on the xp (which does not have IIS running
locally)

That led me to believe that you wanted to open the project from that box.
I think you meant "open the project from the xp".

re:
>I can probably open the Project From Web on the 2003 server.

Yup, you probably can.

re:
>Thanks

You're quite welcome.
Good luck, and let us know how you do, OK ?


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:Oi***************@TK2MSFTNGP05.phx.gbl...
>Hello Juan.

I don't want to install IIS on my XP Pro box.

However your information on opening a Project From Web gives me an idea
to try. I can probably open the Project From Web on the 2003 server.

I should probably pay more attention to the menu options.

Thanks,
Tony

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
>>re:
When i try to open the project on the xp (which does not have IIS
running locally)
connected to the Windows 2003, i get an error that says it can't find
localhost.

You *must* install IIS on that computer if you want to be able
to access a VS 2003 project copied to that computer.

First, install IIS on that XP Pro box.

Then, try to access the project.

When you open a Web project, the system opens it using the Web access
method
(file share or FrontPage Server Extensions) last used for the project.

To open an existing Web project that is not part of source control

1. On the File menu, point to Open, and then choose Project From Web.
2. In the Open Project From Web dialog box, enter the URL of the Web
server where the project is
located, and then click OK.
3. In the Open Project dialog box, double-click your Web project's
folder.
4. Double-click the appropriate project file to open the project.

The Web project opens and its files are listed in Solution Explorer. If
the project could not be
opened, an error message is shown that allows you to try another Web
access method or to
work offline.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl.. .
Hello.

I'm developing and testing a web application using VS.NET 2003, VB,
.NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.

How do I move this project/solution from a local development xp pro
computer which uses
IIS/localhost, to another xp pro computer that is on a Windows 2003
server domain. I want to be
able to use the Windows 2003 server IIS instead of localhost.

I'm not trying to deploy the project for end user use. I'm still
developing and want to now
continue development on new xp that is part of the Windows 2003 server.

When i try to open the project on the xp (which does not have IIS
running locally)connected to the
Windows 2003, i get an error that says it can't find localhost.

Any help would be gratefully appreciated.

Thanks,
Tony




Oct 23 '06 #29
See "Remote IIS Web Sites" :

http://msdn2.microsoft.com/en-us/library/h17hytcs.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:OG**************@TK2MSFTNGP03.phx.gbl...
Hello Juan.

When i try to open "Project From Web", i enter the server name in the url box, select the web site
i want to open and it gives this message: "Documents in this folder are not available. The folder
may have been moved or deleted, or network problems may be preventing a connection to the server."

Thanks,
Tony

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP06.phx.gbl...
>What made it a bit difficult to diagnose your problem is that you stated that :
>>When i try to open the project on the xp (which does not have IIS running locally)

That led me to believe that you wanted to open the project from that box.
I think you meant "open the project from the xp".

re:
>>I can probably open the Project From Web on the 2003 server.

Yup, you probably can.

re:
>>Thanks

You're quite welcome.
Good luck, and let us know how you do, OK ?


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:Oi***************@TK2MSFTNGP05.phx.gbl...
>>Hello Juan.

I don't want to install IIS on my XP Pro box.

However your information on opening a Project From Web gives me an idea to try. I can probably
open the Project From Web on the 2003 server.

I should probably pay more attention to the menu options.

Thanks,
Tony

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl.. .
re:
When i try to open the project on the xp (which does not have IIS running locally)
connected to the Windows 2003, i get an error that says it can't find localhost.

You *must* install IIS on that computer if you want to be able
to access a VS 2003 project copied to that computer.

First, install IIS on that XP Pro box.

Then, try to access the project.

When you open a Web project, the system opens it using the Web access method
(file share or FrontPage Server Extensions) last used for the project.

To open an existing Web project that is not part of source control

1. On the File menu, point to Open, and then choose Project From Web.
2. In the Open Project From Web dialog box, enter the URL of the Web server where the project
is
located, and then click OK.
3. In the Open Project dialog box, double-click your Web project's folder.
4. Double-click the appropriate project file to open the project.

The Web project opens and its files are listed in Solution Explorer. If the project could not
be
opened, an error message is shown that allows you to try another Web access method or to
work offline.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Tony Girgenti" <tony(nospam)@lakesideos.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl. ..
Hello.
>
I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.
>
How do I move this project/solution from a local development xp pro computer which uses
IIS/localhost, to another xp pro computer that is on a Windows 2003 server domain. I want to
be
able to use the Windows 2003 server IIS instead of localhost.
>
I'm not trying to deploy the project for end user use. I'm still developing and want to now
continue development on new xp that is part of the Windows 2003 server.
>
When i try to open the project on the xp (which does not have IIS running locally)connected to
the
Windows 2003, i get an error that says it can't find localhost.
>
Any help would be gratefully appreciated.
>
Thanks,
Tony
>





Oct 23 '06 #30

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Lori Manney | last post: by
5 posts views Thread by Schoo | last post: by
7 posts views Thread by Chris Hayes | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.