We offer a broadly applicable strategy – including OO source code that you can insert directly
into your existing c# master page(s). The master page code provides for 4 optimized views (desktop, tablet, mobile phone and theatre views) using the same XHTML base. By standardizing to just 4 views, our product helps you strike a consistent balance between device width, pixel scaling and user control in less time. Testing scenarios also become simpler.
VB.NET source code versions are also available. Actually there are 3 project templates in each language, and each is honed to a different base project template starting point in Visual Studio. Incidentally, Mobile ASPX is, in all liklihood, compatible with any responsive design techniques you have in place. We are all about compatibility with this product! And this is demonstrated in the Project1 template. Link to details on project templates and their differences...
We think our code package can help you deliver mobile formats on your custom
web and intranet web forms - fast. For the complete announcement text on Mobile ASPX TechCrystals Code Package, please visit our News and Events page Announcing Mobile ASPX TechCrystals Code Package!
For confidential pricing information – contact us today!
(we will not rent, sell or share this information)
name and a valid email address is required)
Need a little more information?
Read about the – Mobile ASPX - Features and Benefits
More Product Information: Each project has
well-organized documentation of the OO source code differences, highlighting net changes from before and after
Mobile ASPX has been applied (based on Visual Studio base project templates (3 in all)). Similar net change
documentation is provided for all of the files, CSS and base project .aspx differences. There are also
detailed comparison examples of how incompatible HTML can be enhanced to work in all four views, to perhaps handle upwards of 98%, not including new client-side scripting or rewrites. When you just have to hard-code a difference between formats,
it can be done. Examples are included for how to do it in the code-behind. On
the Tegratecs site for example, on the drop-down navigation menu, we change the font size (and also the
direction of expansion) at run time based on the view (using code-behind) in Project2 and Project3. The product also
includes use of a soft-coded set of methods that increases the <ASP:Button> size and button fonts
via a little bit of UI control hierarchy traversal and recursion in the OO code-behind.