Messages
Reply
Edit
Delete06:02 am
3RG0CY0R5
| From: | FoxInCloud support |
| To: | Tuvia Vinitsky |
If you prefer hand-made things, you can undo and redo all your install manually.
You may also, if you prefer, use Console.exe.
You do have the choice.
When trying the latest publish wizard from FAA, it wants to force me to create a xxxtest and xxxprod projects. While this may be the recommended FiC way of doing things, it contradicts the types of systems usually found in development environments, such as a 3 tier develop/test/prod, and it forces the users into developing in a manner he may not wish to do. For example we neer use a xxxprod, because it assumes that test and prod are on the same server and simply is confusing.
New FiC users find this test/prod very confusing.
We have a test server and a production server and are never going to use the test/prod projects -- why force the user to do this?
Also, you create IIS sites (test and prod) which may not be what the user wants, you force a certain scriptmap extension, you force the name of the site in IIS.
you also force the location of the "site" folder. Worse, you create an application pool even if a WWWC pool exists.
Why all this forcing?
It would be nice if we could use publish for establishing sites with our own options, now we do it all by hand.
On my! I just discovered a major flaw - you changed all my FiC existing site to use your new Foxincloud app pool! It does not seem that it is ever possible to use publish if you ever had a fic site already.
Thierry Nivelet (FoxInCloud)
Never explain, never complain (Queen Elizabeth II)