version 10 of WWF

As we know from v10 development road map, v10 is coming out with new HTTP XML API. We obviously love the new approach.

Will you discuss a little more about specific features in the new version?

And doesn't the new version will be ported to ASP.NET [VB]? I think as ASP itself has migrated to ASP.NET, we should also port to that.

Why not?

WWF is a forum which is a part of a large site. Even for small sites it is the core for member managements. Whenever you think, if it is with ASP.NET, it will be easier for developers to integrate WWF into their site. I do not mean only using the forum but also using the functions in the scripts

With ASP.NET you no longer require third party components to install. You can do uploading, image processing and a lot.

Besides, ASP.NET is the next version release of ASP v3.0. If there had been ASP v4.0 wouldn't you be satisfied with porting to v4.0? ASP.NET is ASP v4.0

XML API will be great for integrating with external forum resources. Great Programming skills. Google also provide this kind of API with google apps. But how much of the ppl who use google apps use google API? The number is minor.

-boRg- wrote: When an ASP.NET version is released it will be released as a new product, Web Wiz Forums.NET to run along side the present ASP version, as many people still use ASP and prefer ASP as it is easier to learn and modify than ASP.NET.

Glad to hear that -boRg- :)

I agree that it is a HUGE task to convert WWF to ASP.NET, well, i suggest that because everyone will be porting to ASP.NET eventually. I like this WWF a lot and would love it to have in .NET :)

As ASP will become older and older, it will no longer meet future expectations while ASP.NET comes with lots of flexibility to the developer overcoming the limitations of ASP like ASP can't determine the Time Zone. Third party components will not be a must for most tasks in .NET. How many of Windows users uses windows 2000 professional? Almost everyone ported to newer versions. Because newer versiions are feature rich. And when some thing is enriched with features, it is more tough.

-boRg- wrote: The new HTTP XML API is still written in ASP, but you use HTTP post or get to send data to the API which then returns an XML result which you then parse, using something like the MS HTTP XML object.

I have already said this is a great approach. Making compatible with ANY application. XML API will allow a developer to access WWF even from Desktop applications, mobile devices... and so on. I appreciate and welcome this effort very much for the great programing skills and the contribution of -boRg- and all others behind it. This will surely make WWF a jump ahead and us bring smile on face :)

As I said there are sites where ppl can access various XML APIs like google Apps can be accessed and managed trough google API. But how many of google app users impolement the google API? Well, the ppl those don't use google API is because they need to code it. They have come to google because they were looking for 'ready made' products or they can't afford having own servers. In either case, fewer ppl are using the API.

So, I can doubt how many of the WWF users will be using WWF API if it's not developed and delivered with WWF download.

Alternatively, this API can be developed after porting to ASP.NET. It doesn't make any difference, though.

Or, as the API is being developed, you may consider the core, membership management to be in the ASP.NET version and the forum, calender and other modules will be using that API. does this sounds considerable?

v 10
i wish i can find upload , Private Mesenger, and Calender again
that free for me.