I was asked to generate a list of all our BES users, including their name, phone number, PIN, IMEI and device number. Sure, I could have copied/pasted this data out of the BES management utility, but what fun is that?
It turns out that it’s really easy to query the BESMGMT database for this list.
SELECT
uc.[DisplayName],
sdms.[PhoneNumber],
uc.[PIN],
sdms.[IMEI],
sdms.[ModelName]
FROM
[dbo].[SyncDeviceMgmtSummary] sdms
INNER JOIN
[dbo].[UserConfig] uc on sdms.[UserConfigId] = uc.[Id]
Description
If you enjoy working on a variety of cutting edge web applications ranging from eCommerce apps to Social Networking sites then this position might be for you! MBC is seeking to hire a talented and passionate developer with a deep understanding of ASP.NET and the .NET framework but who also likely knows their way around windbg. Experience with standards-based XHTML, CSS, JavaScript and AJAX is a must. The position is based out of Richmond Hill, Ontario (just outside of Toronto). Office environment is young and casual.
Experience
Degree or certificate in Computer Science, Computer Engineering or college level application development program. Some experience developing production applications required.
Responsibilities
Requirements
Additional Assets
Salary
Commensurate with experience.
To apply for the job
Candidates will be required to provide sample source code that demonstrates strong knowledge of C# and ASP.NET. An application implementing an n-tier design is highly recommended. Additional consideration will be given to candidates who provide sample code using .NET 3.0/3.5 technologies such as LINQ, WCF, WPF.
Back in October I opened up a MS Connect feedback item about a validation error I was receiving with a XHTML Strict site that used a ScriptManager with history support. The site would fail W3C validation because the ScriptManager emits an IFRAME (when history is enabled) , and an IFRAME is not part of the XHTML Strict spec. I just thought I’d provide the official word from Microsoft on this issue: XHTML Strict is not supported by ASP.NET!
XHTML strict is not supported by ASP.NET. Only transitional doctypes are supported, which enables iframes. Furthermore, the history feature can't be made compatible with IE 6 and 7 without using an iframe.
Posted by Microsoft on 11/12/2008 at 12:34 PM
I was recently reviewing a customers eCommerce site and I noticed that the “Please Wait” page that occurs after completing an order but before you view the order was taking a long time to load. Using Firebug I traced the issue down to an external script that was taking it’s sweet time to download; it was for affiliate tracking on a 3rd party site.
I’m all for tracking, but not at the expense of performance. Though I haven’t seen an affiliate/ad partner use the defer attribute on their script tags before, there is good reason for you to add it. Consider the following example:
SlowRequest.aspx is just an ASP.NET page that after a 2 second delay, returns some JavaScript (not my finest code I might add)
Sure enough, for the first two seconds, all you see is
And finally (2 seconds later)
Luckily for this example, this information isn’t overly pertinent – but if it were my order status, it would be. Luckily a quick defer=”defer” attribute on your script tag and the wait is gone; the external script is loaded after the DOM is ready:
October 27, 2008
TORONTO - OrderDynamics Corporation, an on-demand eCommerce solution provider, is pleased to announce its new website.
Since 2006, OrderDynamics has had a website that focused more on the technical details of their solution. The new website, and company logo and colors, is designed to provide visitors with a view to the entire OrderDynamics solution, not simply technical details.
"Our success comes from our overall approach, and we wanted this reflected in our brand and website going forward." Michael Benadiba, CEO and founder of OrderDynamics Corporation. The new website contains new content areas that describe all major aspects of the eCommerce solution. The design itself is significantly less busy, more simplistic, and easier for potential Clients to find what they need -all underlying themes meant to support the company philosophy. "The format of the website is exciting for us. Shortly, we will be providing specific content to explain to potential Client’s how we solve real problems for online merchants." Benadiba says.
OrderDynamics Corporation is a privately owned company that provides turn-key eCommerce solutions to businesses looking to grow their online sales. The success of OrderDynamics is highly attributed to its response to real Client requirements and Dynamic Merchandising concepts which provide superior control and help drive revenue. The OrderDynamics solution is designed for online merchants and services different business such as retail, manufacturing, business-to-business, complex online retail, and more. OrderDynamics officially launched its solution in 2006 after 2 years of research and development.
Michael Benadiba
Chief Executive Officer
OrderDynamics Corporation
1+ (866) 559-8123
news@orderdynamics.com
ASP.NET 3.5 SP1 introduces script combining to the ScriptManager. To take advantage of this feature with your own scripts, you simply wrap you <Scripts>...</Scripts> block with a <CompositeScript>...</CompositeScript> block. This is great, but if you've spent any time analyzing your site with a HTTP tracing tool like Firebug, Web Development Helper or Fiddler, you'll notice that the MS AJAX Runtimes (MicrosoftAjax.js, MicrosoftAjaxWebForms.js) is still served up separately. It turns out that getting these to be served as part of the combined script is relatively straight forward and entails manually including the scripts within your <CompositeScript> block. Since the names are unique, the ScriptManager will not re-add the runtime libraries. The final result looks like:
<asp:ScriptManager runat="server" ID="scriptManager">
<CompositeScript>
<Scripts>
<asp:ScriptReference Name="MicrosoftAjax.js" />
<asp:ScriptReference Name="MicrosoftAjaxWebForms.js" />
<asp:ScriptReference Path="~/scripts/YourScript.js" />
</Scripts>
</CompositeScript>
</asp:ScriptManager>
