Skip to main content

WOWZAPP 2012: Worldwide Global Hackathon for Windows -- Bucharest, Romania

Everyone on Earth already knows what will happen at the end of this month. Yes, you are right, Windows 8 will be launched. Not only this, Windows Phone 8 will be lunched in this month also. With this occasion Bucharest will be the host of WOWZAPP 2012: Worldwide Global Hackathon for Windows.
Sounds good and it will be a great event. You will have 24h to develop a great Windows Client App for Windows 8.

If you know C# and XAML or JavaScript and HTML5, than you should register NOW.
If you have a great idea of an application for Windows 8, that you should register NOW.
If you have a great idea of an application for Windows Phone that you should register NOW.

In the case you need something in backend; you will receive a six month subscription for Windows Azure.
What a great event! See you there.

Comments

  1. Nice :) Will be able to buy Win8 tablets and phones in Romania at launch date?

    ReplyDelete
    Replies
    1. @Tudor, you have money to spend. :D

      Delete
    2. Yes I have :) It's not a launch without the product being available..

      Delete
  2. Nokia phone is launched . I think window 8 features are little bit different from 7. I am waiting to get win8.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see