J
John_Doe
Can anyone clarify what the difference between these two choices is
when developing website? I have IIS installed too, so I can pick this
too if there is a reason.
From the point of view of sharing the code with other developers and
keeping source in VSS File System seems to be more flexible choice.
However, my current understanding is that when you keep it in the File
System and start it from Visual Studio it runs on Web Server built in
in VS, and if it is created on local IIS then it runs on local IIS
(please correct me if I am wrong). In production it will of course run
on IIS so if there are some differences in behavior between Web Server
built in VS and IIS they may not become obvious during development,
which is not a good thing.
Is there any difference in functionality of Web Server built in in VS
and IIS? I wouldn't be surprised if Web Server built in VS has reduced
functionality compared to IIS.
One approach that I found is to create a virtual directory in IIS that
point to the folder in the File System containing the website. Website
is then created on local IIS but physical location is wherever I
choose. This approach seems to be the best to me.
when developing website? I have IIS installed too, so I can pick this
too if there is a reason.
From the point of view of sharing the code with other developers and
keeping source in VSS File System seems to be more flexible choice.
However, my current understanding is that when you keep it in the File
System and start it from Visual Studio it runs on Web Server built in
in VS, and if it is created on local IIS then it runs on local IIS
(please correct me if I am wrong). In production it will of course run
on IIS so if there are some differences in behavior between Web Server
built in VS and IIS they may not become obvious during development,
which is not a good thing.
Is there any difference in functionality of Web Server built in in VS
and IIS? I wouldn't be surprised if Web Server built in VS has reduced
functionality compared to IIS.
One approach that I found is to create a virtual directory in IIS that
point to the folder in the File System containing the website. Website
is then created on local IIS but physical location is wherever I
choose. This approach seems to be the best to me.