|
Home > Archive > IIS Server > June 2005 > transfer IIS development platform to SOHO
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
transfer IIS development platform to SOHO
|
|
| realraven2000@hotmail.com 2005-06-21, 8:00 am |
| Hi,
I would like to transfer my ASP development from the office to home.
platform
Visual Interdev 6.0
SQL Server 2k
IIS 5.1
are installed on my XP Pro workstation.
How do I transfer my web project to my local server? I can not get the
"Add to master web" option in Visual Interdev is there a setting in it
(or the registry) to tell it where the web server is? Do I need to
install IIS first, then Visual Studio over it?
Or is there a setting in the IISAdmin snapin? Could it be a problem
with my free ZoneAlarm firewall?
or maybe I go about this the wrong way I was opening the project file
that I copied from my dev laptop at work - maybe I need to create a new
project and add all files?
Will my test pages be visible to the outside world when I am online (I
want to avoid this)?
Also, do I need to install frontpage 2000 Server extensions for working
with Visual Interdev?
I also installed the IISAdmin tool, looks cool; I tried adding my
existing project via this but I still got errors when loading up
Interdev - I think I am only missing the connection from Interdev to
IIS (the Server bit). Almost
ready to develop at home now :-) Can't really spend too much time at
the office as I amsharing the car with my wife and cars are bl*dy
expensive here in IReland 
cheers & tia
Axel
| |
|
| Sorry I should probably have mentioned that I am an ASP & IIS newbie;
just looking for a quick and dirty way to do my development from home
and to cover a bit more mileage outside the office, not interested in
hosting, being online or high performance for this... cheers
btw ony got bad dialup so I need a solution that does not involve the
www for testing.
| |
| David Wang [Msft] 2005-06-22, 7:54 am |
| I honestly have no idea about Visual Interdev and IIS5 -- pardon the pun,
but that's like ancient stuff. :-) Your question is really more with Visual
Interdev. IIS has no idea what a "web project" is (it just thinks it is a
bunch of files).
How Visual InterDev and IIS work together is this:
- IIS runs to serve web pages and to respond to HTTP requests
- FPSE is used by Visual InterDev to configure IIS
- Visual InterDev uploads/downloads files at-will to implement the notion of
a "Web Project".
So, it is really your responsibility for ensuring that Visual InterDev on
one computer can communicate with IIS on another; as well as what needs to
be installed to support projects. IIS really knows nothing about it - it is
just a platform that other applications use to provide services and
behaviors.
Now, firewalls like ZoneAlarm are known to cripple IIS as well as prevent
access to the web server, so it may be a culprit that is preventing tools
like Visual Interdev from working. But once again, that is not a Microsoft
product so you want to obtain support from the providers of ZoneAlarm.
You may want to look at the next generation tool to do the same things --
Visual Web Developer.
http://lab.msdn.microsoft.com/express/vwd/default.aspx
If you think Visual Interdev and IISAdmin look cool, wait until you see what
Visual Web Developer allows you to do...
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Axel" <realraven2000@hotmail.com> wrote in message
news:1119348486.574179.143080@f14g2000cwb.googlegroups.com...
Sorry I should probably have mentioned that I am an ASP & IIS newbie;
just looking for a quick and dirty way to do my development from home
and to cover a bit more mileage outside the office, not interested in
hosting, being online or high performance for this... cheers
btw ony got bad dialup so I need a solution that does not involve the
www for testing.
| |
|
| Hi David,
thanks for the information. I am using the mentioned versions of
software because these are the ones my colleagues use and I do not want
to introduce versioning problems. IIS 5 is simply installed on our test
server and Visual Studio 6 is the version that everyone at the office
uses. However we also have a copy of VS 2005 lying around AFAIK nobody
has dared to install this one yet. The problem with anything after VS6
is that nobody knows how this will support backwards compatibility
since the focus has shifted so much to DOT NET which we are currently
not using.
> If you think Visual Interdev and IISAdmin look cool
actually, no! If I had a choice for web developement I would totally
prefer to use dreamweaver MX, but we do not have licenses for this at
work.
If you look at the Visual Studio product line, the only version 6 IDE I
would consider "mature" is the one for Visual C++. VB and InterDev have
a lot usability issues, starting from the way screen space is wasted,
dockability and non cohesive ness; If you compare it to DW Visual
Interdev is not a great product. But I use it because there is licenses
and (some) support at the office.
I might consider trying out Visual Web Developer if you could clarify
that I am not forced to use DOT NET technology for my development.
regards
Axel
| |
| David Wang [Msft] 2005-06-29, 5:53 pm |
| Well, comparing Dreamweaver against Visual InterDev or even Visual Studio 6
is not exactly a fair comparison. Both Visual Studio 6 and Visual InterDev
are more than three versions from the latest release of current tools.
Dreamweaver MX is a flagship product just versioned last year. And comparing
5+ year old UI to current standards is rather odd...
I asked members on the Visual Web Developer product team, and they indicated
that there are two things that you must distingish in what you want to do:
- Designer surface - layout and design the web pages, graphics, thumbnails,
CSS, etc
- Code behind surface - the dynamic code invoked by parts of the layout to
do interesting work
Although Visual Web Developer does not force .Net development when running
it (it has a simple check for .Net Framework being installed, but it's
pretty easy to work around), you'd be missing out on most of the features
related to code behind (that uses .Net), though you'd still have basic
VID-level Intellisense support for ASP. Since ASP is not structured, there's
not much more you can do without introducing proprietary organizational
constructs. As for the designer surface, you will have WYSIWYG composition
of HTML/ASP pages comparable to FrontPage, but when it comes to graphic
widgets, image manipulation, etc, FrontPage would be better suited.
Now, one has to note that Visual Web Developer is free - $0 to download and
no real strings attached - and primarily addresses the lack of an ASP.Net
development environment. It isn't targetting ASP, though the feature
coat-tail is certainly long enough to make ASP more comfortable.
It costs nothing to try out, and as with all of Visual Studio, there is a
great deal of product transparency and support -- the product team members
actively listen to anyone in the community (free to join), definitely made
many product changes according to community feedback, as well as solicit and
investigate any issues reported by the community to improve product quality.
So, you are definitely not isolated nor alone (unless you want to be), and
if you want a better product, voice your opinions because they will be
heard. Otherwise, you are just silently griping and hoping for psychics to
read your mind... and we all know how effective that can be.
Visual Web Developer landing page:
http://lab.msdn.microsoft.com/express/vwd/default.aspx
Visual Studio 2005 landing page:
http://lab.msdn.microsoft.com/vs2005/
Note the open solicitation for product feedback, suggestions, Q&A, and issue
reporting/tracking. You can be as involved as you want to be.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Axel" <realraven2000@hotmail.com> wrote in message
news:1119866787.347609.44570@g49g2000cwa.googlegroups.com...
Hi David,
thanks for the information. I am using the mentioned versions of
software because these are the ones my colleagues use and I do not want
to introduce versioning problems. IIS 5 is simply installed on our test
server and Visual Studio 6 is the version that everyone at the office
uses. However we also have a copy of VS 2005 lying around AFAIK nobody
has dared to install this one yet. The problem with anything after VS6
is that nobody knows how this will support backwards compatibility
since the focus has shifted so much to DOT NET which we are currently
not using.
> If you think Visual Interdev and IISAdmin look cool
actually, no! If I had a choice for web developement I would totally
prefer to use dreamweaver MX, but we do not have licenses for this at
work.
If you look at the Visual Studio product line, the only version 6 IDE I
would consider "mature" is the one for Visual C++. VB and InterDev have
a lot usability issues, starting from the way screen space is wasted,
dockability and non cohesive ness; If you compare it to DW Visual
Interdev is not a great product. But I use it because there is licenses
and (some) support at the office.
I might consider trying out Visual Web Developer if you could clarify
that I am not forced to use DOT NET technology for my development.
regards
Axel
|
|
|
|
|