|
|
 |
News
|
|
 |
|
|
|
|
|
| Tuesday, June 17, 2008 |
|
Switching on the (Silver) Light for Enterprises
By Navot @ 8:35 AM :: 594 Views ::
1 Comments ::  :: Announcments, Talk of the day, Silverlight
|
|
Silverlight may be poised to light up the Web but which SDK are you going to use to get your Line of Business Silverlight app's up and running fast, how does Windows Forms sound to you?
The Visual WebGui (VWG) 'on-server' web paradigm has now been implemented for Microsoft Silverlight. It simplifies Silverlight line of business (LOB) development with a proven 90% cut in development time while it empowers it as a GUI for LOB applications.
Gizmox, the company behind the Visual WebGui (VWG) open source platform, has been cooperating with Microsoft in the development of VWG server-empowered Silverlight. A fully functional Beta version will be released beginning of July 2008.
Now, VWG SDK can be used for rapid development of fully blown, data-centric, enterprise-level Microsoft Silverlight applications.
VWG On-Server Empowerment
The move to Web 2.0, AJAX and Silverlight has created problems for LOB applications as it provides them with less than adequate solutions for security concerns, cost-effective development cycles and support for complex interactions in data-centric applications. It is lacking too in options for off-line, desktop and smart client operability. The good news is that the 'On-Server' web paradigm, implemented by VWG, provides solutions to all of these concerns and needs. Read more on VWG 'On-Server' paradigm. See a presentation about VWG 'On-Server' paradigm. A 90% Cut in the Development Cycle without Compromising Silverlight's Rich Graphics
Until now, most of the controls needed for Silverlight LOB applications were missing. Now developers can use VWG's VB6-like designer, dragging and dropping over 60 Windows Forms controls to build Silverlight applications. VWG is as much a revolution in simplifying development in AJAX / Silverlight as VB6 was, in its time, for desktop applications. See real-world testimonial.
This methodology has a real-world, field-proven track record for simplifying development and saving time and resources by 90%. It is currently the fastest method of choice for a migration path to Silverlight and it does it without losing any of Silverlight's rich capabilities - still allowing you to use Expression Blend for styling. There's no need for retooling, retraining or fighting to stay on the learning curve. Once you've made the simple transition you will be more productive than ever. Refer to the real-world experiences of those who've tried it, who report the development experience is the same whether you develop VWG DHTML or Silverlight applications: MVP Jonathan Goodyear in his article, Simplicity at last, MVP Rick Strahl in his article, Visual WebGui and a LINQ to SQL quirk, SAP on their experience of developing a VWG application see the TV interview or read SAP's test case and Joel Hulen in a description of his development experience: " in few weeks I was able to build an OWA application"
Client Remains Thin Regardless of Application Size, Giving Desktop-like Performance
VWG automatically downloads a small kernel of 250K into the browser when the VWG application (DHTML or Silverlight) is first approached (non exe kernel), and that's it! The client remains thin with no data or logic. A VWG pipeline, optimized for standard HTTP, takes care of the server-client communication, optimizing it to a degree not previously experienced on the Web. An average round trip is made up of less than 1K of Meta data. Moreover, not every user interaction causes a round trip - there is an algorithm that handles user interaction requesting server updates only on critical user interaction. This protocol is the reason that the user experience resembles that of a desktop. It lends itself to Silverlight optimization in such a way that it actually enhances the performance of Silverlight applications when they run on top of VWG. Read more about VWG optimization and performance.
Eliminating the Second Biggest Setback for Web LOB Applications – Security
Analysis indicates that the second biggest concern of AJAX, and now Silverlight, for the enterprise is security. They are both deemed as insecure. VWG doesn’t open services, nor does it transfer data or logic to the client. A VWG application uses one pipeline with only Meta data flowing back and forth which makes interception impossible, and that single pipeline can be further secured using standard ASP.NET security, WCF. This level of built-in security is unprecedented on the internet. It meets the strictest US army security requirements and can therefore be used for deploying sensitive enterprise systems, such as CRM and ERP, on the web.
This architecture lends itself again toSilverlight making it secure for LOB applications.
Silverlight or DHTML: A Safety Net for non-Silverlight Users
Many development shops are still sitting on the fence to see where Silverlight is going. Many say that if they had a default optionfor users who still haven't installed the Silverlight plug-in they would jump into Silverlight without hesitation. VWG allows for single development and dual deployment to either HTML or Silverlight. This lets developers cater for all their users whether they have installed Silverlight or not. Both will be able to access the application, with the Silverlight users enjoying a richer GUI.
Scalability up to Web Farms
VWG is fully scalable - at least as much as ASP.NET, which it uses as its underlying technology - as proved in real-world tests. For large enterprises and high volume traffic, such as that seen in typical high traffic B2C applications, VWG provides an enterprise server that scales over web farms and gives redundancy protection. This allows FaceBook-like applications to be built with VWG and now with Silverlight as the presentation layer. Read more... ROI that Outrivals Citrix without Citrix's Limitations
VWG provides for RAD development of AJAX / Silverlight applications. As such the outcome is a fully enabled Silverlight or DHTML application. Due to the RAD nature of its development process, VWG can provide the same ROI as Citrix but without the limitations. In this respect, VWG is big news for those seeking to port applications to the Web with minimum expenses. See the article comparing VWG and Citrix in terms of use cases, performance, security and ROI. It gives the developer RAD capabilities, without limiting any of the options for extending or customizing and provides a smooth migration path for web and Windows forms developers. Developers, read more. Coming Soon: Utilities for Migrating from VB6 and WinForms to VWG (Silverlight and DHTML), Real-time Messaging and Mash-up Integration
VWG will soon be shipping new servers and utilities that will give VWG an even better ROI.
Even now, pure WinForms applications can be migrated to VWG just by changing namespaces, something that is already widely used by VWG community members. It will soon be made simpler still with the automation of such migrations. There are Microsoft tools available to migrate from VB6 to WinForms and therefore VWG can be used for fast and rapid migration to cutting-edge Silverlight technology. The result is a complete flattening of the learning curve.
Mash-up capabilities are inherent in VWG's architecture, desktop or client-side alike. VWG will shortly introduce a server and utility that will allow rapid mash-up for application integration. Visual WebGUI can be used to present and mash up cross platform applications with VWG as the central application or integrated into other applications.
Real-time messaging will allow real-time presentation in the VWG application for cases such as the displaying of current share values.
All these will be enabled for VWG Silverlight applications as well, as capabilities inherent in the VWG platform.
|
|
|
|
|
| Sunday, June 08, 2008 |
|
White paper: On –Server AJAX, a paradigm shift that optimizes AJAX and now Silverlight for enterprise's usage
By Navot @ 2:08 AM :: 329 Views ::
1 Comments :: :: Talk of the day, Silverlight
|
|
Overview
AJAX, a term coined by Jesse James Garret from Adaptive Path in 2005 has become a ubiquitous term for highly interactive and responsive web applications.
The evolution of the web closely resembles the evolution of desktop computing moving from the age of “dumb” terminals or the mainframe computing paradigm into the client server computing paradigm, into a new paradigm shift called On Server AJAX and now SILVERLIGHT computing.
The move to AJAX / SILVERLIGHT has left enterprises with no adequate solutions for security concerns, cost effective development cycles, and support for complex interactions and options for off-line operability.
On Server AJAX / SILVERLIGHT offers revolutionary solutions to those concerns and needs.
Typical AJAX / SILVERLIGHT = Client Server
Client side AJAX / SILVERLIGHT is similar to Client Server computing in that it shifts much of the application logic to the client. It enables savvy Javascript developers to develop applications which make the most of the browser and the computer they’re running on, while freeing the server to focus on non UI tasks. Client side AJAX / SILVERLIGHT suggests that application flow and UI related logic be developed in DHTML and Javascript all connecting with server side “services” which can communicate as XML web services, plain text or JSON (JavaScript Object Notation).
The trend to adopt AJAX / SILVERLIGHT has not passed over enterprises and line of business applications. Developers are constantly trying to cope with ever growing demands while improving the overall user experience. However, AJAX / SILVERLIGHT have brought on new challenges when used in the enterprise. Securing direct connections between the client and server “services” is problematic; needing to master both client-side (Javascript, DHTML) and server-side technologies is a burden and ensuring consistent performance regardless of bandwidth and desktop computing power is near impossible.
On Server AJAX / SILVERLIGHT = On Server computing
The On Server AJAX / SILVERLIGHT paradigm shift is lead by Visual WebGui. The approach, coined by Guy Peled as “On- Server AJAX / SILVERLIGHT”, means the entire application flow, UI logic and validations are developed and processed on the server while the browser serves as a “display” for the output and a “receptor” for user input. As with Server based computing, On- Server AJAX / SILVERLIGHT simply reflects the “screens” to the client, captures user input from the client and reflects the incremental changes back to the client all over a highly optimized communications channel. In the case of On- Server AJAX / SILVERLIGHT there is no need to consider the “screen” as a purely graphical representation of the application – a bitmap, but rather it can be considered as a series of related components which change according to the application logic. In effect this is similar to how X-Windows communicates changes to X-Terminals by transferring component changes between the client “host” and the server’s state.
On Server AJAX / SILVERLIGHT, opens the path for enterprises to take advantage of the AJAX / SILVERLIGHT revolution
Deploying complex line of business applications on the web has traditionally required either rewriting the application using web oriented technologies and development patterns or employing server based computing platforms such as Citrix and Windows Terminal Services. These platforms have grown in popularity as a solution for supporting heavy deployments of existing client-server line of business applications. However, they are an expensive solution which usually serves as a last resort.
The On Server AJAX / SILVERLIGHT paradigm shift allows for the first time, to support deployments of complex line of business applications with unprecedented simplicity, bullet-proof security and unlimited complexities all at a dramatically reduced cost. With On Server AJAX / SILVERLIGHT applications can run in desktop or web mode using the same source code, and can be migrated from legacy code without requiring rewriting the application.
Eliminating the security hazard, facilitating enterprises usage
Client side AJAX / SILVERLIGHT requires the browser to connect directly to a web service or even a raw data provider. Since this is a very dangerous practice, developers usually connect to a proxy application service which understands the “context” of the request by recalling session state. There are numerous articles discussing the security challenges presented by client side AJAX / SILVERLIGHT. For consumer internet sites, the improved user experience has usually overridden the security concerns. However, for enterprise applications this is still a key concern.
On Server AJAX / SILVERLIGHT utilizes a client side “rendering” engine which communicates with the server over XMLHttp. The rendering engine uses a proprietary protocol to incrementally update the view. The client never consumes data or services directly since all of the application logic, UI logic and data access is handled on the server. The client simply connects to the “view” on the server and therefore never compromises security. Furthermore, since a proprietary protocol is used to correlate view state between the server and the client, it’s a greater challenge to override, eavesdrop or hack.
In addition in On -Server AJAX / SILVERLIGHT, the only data that is delivered to the client is data that can be viewed on the client meaning there is never any sensitive data that may be required for logic or validation beyond what is rendered and seen by the user on the screen.
Developer Productivity in building complex enterprise level GUIs, as never before
While AJAX / SILVERLIGHT have brought a significant improvement in user experience and application complexity, it has also brought about a dramatic increase in the complexity of development and testing. Furthermore it requires developers to master a number of different languages: Javascript, HTML, CSS and XML on the client as well as the server side language being used to develop the underlying business logic.
A complex web application such as Microsoft Outlook Web Access or Salesforce.com also requires serious architecting skills in order to maintain application state, security and data integrity between local cached data and server side data. While historical, page based web applications were deemed easier and cheaper to develop then their desktop counterparts, developing a complex client based AJAX / SILVERLIGHT web application is harder and more expensive to develop then an equivalent client-server application.
The On Server AJAX / SILVERLIGHT paradigm enables the developer to use a single language and programming model in order to design the application UI and the underlying logic. In addition it alleviates the need to understand and deal with the web’s innate statelessness. Instead, On Server AJAX / SILVERLIGHT offers the use of well known design patterns and tools such as WinForms to design and develop highly interactive, data rich applications with the same productivity of desktop applications. This enables migrating existing desktop applications to On Server AJAX / SILVERLIGHT without rewriting them.
Simplifying the architecture from a loosely coupled, stateless, multi-language mix into a tightly coupled, object oriented, single language environment means less time is spent on architecture, development, debugging and maintenance. On Server AJAX / SILVERLIGHT dramatically improves ROI and TCO. In addition the layout and interaction design are not as limiting as most web oriented application development platforms.
On Server AJAX / SILVERLIGHT developers also enjoy re-use of well honed skills (WinForms) and existing code which further improves productivity. Furthermore, the same code can be used to create desktop and web based versions of the same application.
For technological guru opinions on On Server AJAX / SILVERLIGHT productivity see:
MS MVP RICK STRAHL on his blog: "Visual WebGui is intriguing. It's ridiculous how productive you can be with a tool like this compared to building an ASPX page. But somehow it feels like cheating...". "
Highly optimized performance enhances end user experience
Client side AJAX / SILVERLIGHT is meant to improve the responsiveness of the client. In most cases the user experience is improved, however it can have a dramatic effect on server load. Frameworks send across hundreds of lines of Javascript code over and over between requests, necessitating heavy I/O on the host web server generating a “large” bandwidth profile. Client side AJAX / SILVERLIGHT frameworks rely on the processing power of the client to handle caching, serialization, validation and paging. Performance varies according to the available resources on the client. Lower memory and slower CPUs could have an adverse effect on the user experience.
On- Server AJAX / SILVERLIGHT only needs to transfer the rendering engine code once after which only state and data changes are transferred as required. Ultimately this requires more client/server round trips; however the bandwidth profile is kept at a minimum. This results in a highly responsive application which utilizes fewer resources enabling servers to handle more concurrent users. In On Server AJAX / SILVERLIGHT the client only handles rendering of the current view state. This means that less client side objects and data need to be processed on the client (for rendering purposes) resulting in less client side resources being required. Ultimately this ensures all users receive uniform performance regardless of their memory and CPU limitations.
MS MVP WIKTOR ZYCHLA on his blog: ' VWG is the undoubted winner it did a great job of serving the highest number of requests per second"
Summary
As more and more applications turn to the web as the de-facto deployment platform the need for tools and development patterns to support complex user interfaces will grow. AJAX / SILVERLIGHT is a key component of modern web applications and will continue to serve as the basis of many rich internet applications. AJAX / SILVERLIGHT are just a term, there are numerous AJAX / SILVERLIGHT solutions and techniques available and not all are created equal. As a whole, the On Server AJAX / SILVERLIGHT paradigm led by Visual WebGui provides a better way to design , develop and deploy complex, secure, robust applications in an effective and familiar fashion.
For samples of applications built using On Server AJAX see:
Bibliography:
“Cognitive Load and the Superiority of Server-Side AJAX GUI Frameworks”
http://blogs.pathf.com/agile AJAX / Silverlight/2006/08/cognitive_load_.html
“AJAX (programming)” – Wikipedia
“Server –Side AJAX / SILVERLIGHT for the Enterprise”
“What are AJAX”
http:// AJAX / Silverlightpatterns.org/What's_ AJAX
“ AJAX alert raises security, scalability issues”
|
|
|
|
|
| Saturday, June 07, 2008 |
|
VWG's On-Server Web model, is as scalable as ASP.NET AJAX and apparently more
By Navot @ 9:59 AM :: 496 Views ::
0 Comments :: :: Announcments
|
|
One too many, I have been asked; the answer is, yes VWG's On-Server Web model, is as scalable as ASP.NET AJAX and apparently more
The model gets high attentions from developers who keep questioning this model scalability.
Well, here is a more detailed answer.
On-Server Web is based on optimized server-web client connectivity. An average action would generate no more than 1k of Meta data payload. On top there is another optimization by a mechanism that analyzes code, sorting critical events from uncritical ones, calling back, only critical events.
This way highly optimized protocol is achieved.
Sounds complicated? Well, it is not!
The concept is based on the good old "main frame" model, extended for web and updated to include cutting edge AJAX for connectivity and now Silverlight, for a richer presentation layer.
The VWG On-Server client is empty!
When in run time mode, once a VWG application is accessed a 200K kernel, automatically downloaded, and the connection is set.
Logic, data, IP, all run on server. Nothing but that small kernel runs on client.
This is made possible by server state that is being drawn on client using Meta data only. A unique mechanism keeps constant equilibrium between server state and client's and updates only when that equilibrium is broken by user interactions or server updates.
The result, only differential, tiny packets of Meta data are being sent back and force.
See following diagrams.
Drawing 1 - description of On-Server Web paradigm
Drawing 2- description of On-Server – web client connectivity
And now to real world experience:
On-Server Web performance and scalability is attested to, by real world experience as follows:
MVP RICK STRHANAL posts in his blog, following On-Server VWG evaluation:
"… Yup that's not very scalable - and the VWG guys make no secret out of that fact that VWG is not meant for high traffic sites or even for very visual ones..."
After being made aware of the unique architecture, he posts again:
"…well it's interesting. I hooked up Web Application Stress Tool to it and ran through my app and let it rip and surprisingly the throughput is like any other ASP.NET application in terms of number of requests. Now VWG will generate many more requests than your average postback style or even AJAX application, but still if the performance of that throughput with small requests is what I saw in these tests it looks like it should easily scale to at least the threadpool size of users (ie. 100 or so). FWIW, the throughput I saw was 185 req/second which is roughly what I see on a typical simple ASP.NET application. This is with 20 clients and a stress multiplier of 10 with no request limits..."
MVP WIKTOR posts in his blog, real world application testing as follows:
Contest context
More than two years ago we've built a small web application used to collect and print documents required to participate in secondary school final examinations in Poland. The application is used quite extensively by people from all over the country.The application, maturzysta.vulcan.pl, is located here.
…The first version of the application was built as a server-side application: all SelectedIndexChanged events were auto-postbacked and processed on the application server. This caused a lot of trouble since the heavy form had to be sent to and from the server.
The year later we've completely redesigned the application…In the meantime, few promising AJAX frameworks appeared and we thought that it would be possible to go back to the initial version of the application but instead of expensive postbacks we could take the AJAX approach and replace postbacks with callbacks. This could solve all problems: reduce the traffic and still keep the application logic on the server-side.
The test
Microsoft Application Center Test has been choosen as the contest judgement tool. Tests were performed on the Windows XP machine serving as the application server. Exactly 200 sessions have been simulated for 5 concurrent users. Each session has been recorded as the complete user session - forms have been filled with data and dropdown selections have been made. Each session ended with the application showing the print-ready document.
Results
Gathering all results together, we had 2 non-Ajax contestants: pure Web.Forms application, Javascript version of it and 6 Ajax frameworks: Microsoft's ASP.NET AJAX, Ajaxium, VisualWebGUI, ComfortASP.NET, Anthem.NET and Telerik's RAD Ajax.
Regarding requests-per-second we have following results:
|
|
requests-per-second
|
reference
|
|
VWG
|
422
|
198,1220657
|
|
Javascript
|
400
|
187,7934272
|
|
Telerik
|
292
|
137,0892019
|
|
ASP.NET AJAX
|
222
|
104,2253521
|
|
Web.Forms
|
213
|
100
|
|
Anthem
|
133
|
62,44131455
|
|
Ajaxium
|
111
|
52,11267606
|
|
Comfort
|
35
|
16,43192488
|
Regarding number-of-bytes-sent we have following results:
|
|
sent data
|
reference
|
|
Javascript
|
1938800
|
24,23560589
|
|
VWG
|
2066800
|
25,83564589
|
|
Ajaxium
|
5029800
|
62,87407185
|
|
ASP.NET AJAX
|
5600600
|
70,00925023
|
|
Comfort
|
5880400
|
73,50683767
|
|
Anthem
|
6161400
|
77,01942549
|
|
Telerik
|
7293200
|
91,16727918
|
|
Web.Forms
|
7999800
|
100
|
Regarding number-of-bytes-received we have following results:
|
|
received data
|
reference
|
|
VWG
|
23348807
|
29,11700146
|
|
Javascript
|
37121000
|
46,29153905
|
|
Ajaxium
|
47756301
|
59,55423272
|
|
Web.Forms
|
80189600
|
100
|
|
Comfort
|
83742600
|
104,4307491
|
|
Anthem
|
121547800
|
151,575516
|
|
ASP.NET AJAX
|
129531800
|
161,5319194
|
|
Telerik
|
172294800
|
214,8592835
|
Few comments:
- the overall winner is VWG, however the application had to be completely rewritten in order to run under this framework
- the javascript version did not win (even in the bytes-received test!) and though this may seem surprising, it is caused by the script size
- the Ajaxium, Anthem and Comfort reduce the requests-per-second ratio singificantly. The latter two are able to correctly handle dynamic, non-ajax content sent to the browser
- regarding the requests-per-second, Telerik is significantly better than ASP.NET AJAX, however it downloads huge amout of data comparing to all other frameworks
SAP's Asaf Saar, posts in his blog:
"…Then you compile your project and magic, you get a web page with an amazing rich look and feel. Of course, since it’s all AJAX there are no refreshes, no postbacks, and it’s very fast…"
Mark Reed of NetworkD attests:
“Once we went to VWG we saw anywhere from 100%-400%+ improvement in speed…"
High traffic server
Real world experience proves that VWG's On-Server model is scalable.
Visual WebGui is going to ship a new server that allows serialization and floating session that will enable deployment over web farm, thus allowing very high traffic, Amazons like, which usually requires deployment over a web farm. Stay tuned, on this.
|
|
|
|
|
| Thursday, June 05, 2008 |
|
Enterprise Server Beta for scaling over web farm is released
By Navot @ 3:48 PM :: 305 Views ::
0 Comments :: :: Commercial, Announcments, Silverlight
|
|
The Beta version is available for Beta Testers upon registration. We have to limit Beta testers count to 100 only, so if you are interested apply ASAP.
What is VWG enterprise server?
The Enterprise Server beta version 6.1 provides the scaling capabilities & redundancy required in order to store the session state within an external state server that can be either an SQL Server or any state server which is enabled by Microsoft ASP.NET session state.
The Enterprise Server is constructed of 2 main orchestrating components:
- The Enterprise Server’s Windows Service which is responsible of enabling the serialization of the VWG state and assuring the process is done efficiently and optimized.
- The Enterprise Server SDK which is capable to communicate with the Enterprise Server’s Windows service enabling state serialization.
The installation
The installation file presents 2 options:
- Enterprise SDK – which will install the Enterprise Server’s Windows Service locally of the selected .NET runtime version along with the selected VS version’s VWG templates (should be selected when installing development machines).
- Enterprise Server – which will install the Enterprise Server’s Windows Service locally only (should be selected when installing a server).
Those of you interested, can apply through support@visualwebgui.com
|
|
|
|
|
| Wednesday, May 28, 2008 |
|
NEW! White Paper: Visual WebGui - The ROI of Citrix but without the Limitations
By Navot @ 2:28 AM :: 4012 Views ::
1 Comments :: :: Technical, Talk of the day
|
Introduction
We are frequently asked if Visual WebGui (VWG) is not just another Citrix look-alike. Nothing could be further than the truth, for Citrix and VWG offer very different solutions to business requirements that turn out to be far from identical.
There is, of course, a reason behind the question. This paper sets out to disperse the ambiguity and make it quite clear what VWG really is. Interested? Read on.
Why do People Liken VWG to Citrix?
At first sight, one could be forgiven for thinking Citrix and VWG target the same need. They both offer a rapid route to deploying a browser-based business application, they both offer a desktop application user experience, they both allow multi-user access and, perhaps the most significant common ground of all, they both share the concept of a central server to run the mainline data-centric application software.
However, the similarities largely stop there. The following paragraphs explain, in simple terms, the similarities and differences to make it quite clear which of the two technologies are right for your project.
|
| Read
More.. |
|
|
|
|
| Thursday, May 15, 2008 |
|
MSDN Webcast: Programming a Full-Blown AJAX Enterprise Application in 20 Minutes (Level 100)
By Navot @ 8:14 AM :: 694 Views ::
0 Comments :: :: Announcments
|
|
Wednesday, June 18, 2008 8:00 AM Pacific Time (US & Canada)
|
| |
It is all about simplicity when programming next–generation, complex Asynchronous JavaScript and XML (AJAX) applications. In this webcast, we develop a fully blown AJAX enterprise application by dragging and dropping controls using Windows Forms Designer and the Gizmox Visual WebGui (VWG) framework. We extend, customize, and invoke client resources, and we demonstrate how you can cut your development cycle by as much as 90 percent. Visual WebGui is open source, so you can dive into the code.
Presenter: Guy Peled, Chief Technology Officer, Gizmox Ltd
Guy Peled, Chief Technology Officer of Gizmox Ltd, is a renowned expert in Web technologies. He is the developer of two products, the most recent one being Visual WebGUI (VWG). Guy served as chief architect of Gizmox for more than 13 years, specializing on Microsoft platforms. Guy leads the VWG On-Server Web model, lecturing and evangelizing on the subject.
On-Line Registration
|
|
|
|
|
| Thursday, May 15, 2008 |
|
MSDN Webcast: Programming a Full-Blown Silverlight Line-of-Business Application in 20 Minutes (Level 100)
By Navot @ 8:07 AM :: 578 Views ::
0 Comments :: :: Announcments, Silverlight
|
|
Wednesday, July 02, 2008 9:00 AM Pacific Time (US & Canada)
In this webcast, we use the Gizmox Visual WebGui framework to "light up" a fully blown, line-of-business application in 20 minutes. We demonstrate how we make Windows Forms (WinForms) controls available for Microsoft Silverlight browser plug-in applications and how you can style your UI by using fully enabled Microsoft Expression Blend design software. The outcome is a Silverlight application with a very light footprint. As a bonus, the application is secured by design with no open ends to protect.
Presenter: Guy Peled, Chief Technology Officer, Gizmox Ltd
Guy Peled, Chief Technology Officer of Gizmox Ltd, is a renowned expert in Web technologies. He is the developer of two products, the most recent one being Visual WebGUI (VWG). Guy served as chief architect of Gizmox for more than 13 years, specializing on Microsoft platforms. Guy leads the VWG On-Server Web model, lecturing and evangelizing on the subject.
On-Line registration
|
|
|
|
|
| | |