FW/1 .NET port

22 views
Skip to first unread message

John Allen

unread,
Mar 25, 2011, 10:29:05 AM3/25/11
to framew...@googlegroups.com
Hey list.

I am about to embark on some .NET work.

I was wondering if anyone has done/considered/thought about porting FW/1 to .NET.

Is this even a stupid question?

John

Eapen

unread,
Mar 25, 2011, 11:44:29 AM3/25/11
to framew...@googlegroups.com
Don't think anyone has done it yet - but someone has ported FW/1 to PHP.

James Holmes

unread,
Mar 25, 2011, 11:46:47 AM3/25/11
to framew...@googlegroups.com
With MVC3 available in .NET a FW/1 port is unnecessary.

--
WSS4CF - WS-Security framework for CF
http://wss4cf.riaforge.org/

John Allen

unread,
Mar 25, 2011, 12:05:09 PM3/25/11
to framew...@googlegroups.com
I saw the PHP port.

Ill look into the MVC3 stuff. Hopefully it is as clean of a solution.

Thanks.


Sean Corfield

unread,
Mar 25, 2011, 12:33:59 PM3/25/11
to framew...@googlegroups.com
On Fri, Mar 25, 2011 at 8:46 AM, James Holmes <james....@gmail.com> wrote:
> With MVC3 available in .NET a FW/1 port is unnecessary.

Yeah, in general no one writes frameworks for .NET languages because
an MVC framework is essentially built-in.

For the record: I don't do PHP ever (so I'm grateful for Rick
Osborne's port but I would never be able to support it) and I don't do
Windows ever (so the same goes for anyone who decides to port FW/1 to
.NET).
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/
Railo Technologies, Inc. -- http://www.getrailo.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

James Holmes

unread,
Mar 25, 2011, 8:33:27 PM3/25/11
to framew...@googlegroups.com
On 26 March 2011 00:33, Sean Corfield <seanco...@gmail.com> wrote:
> On Fri, Mar 25, 2011 at 8:46 AM, James Holmes <james....@gmail.com> wrote:
>> With MVC3 available in .NET a FW/1 port is unnecessary.
>
> Yeah, in general no one writes frameworks for .NET languages because
> an MVC framework is essentially built-in.

.NET MVC is also convention based, comes out of the box with SES URL
routes and now (with MVC3) comes with a templating engine (Razor) that
replaces that awful aspx rubbish (which was a leftover from winforms).
So people familiar with FW/1 won't find anything too strange moving to
it.

John Allen

unread,
Mar 26, 2011, 3:54:48 PM3/26/11
to framew...@googlegroups.com
Thanks James.

Reply all
Reply to author
Forward
0 new messages