Sevket Seyalioglu

From the free and proven IoC containers/frameworks, please let me know which ones you prefer to use and what makes you choose that one instead of the others?

• Castle Windsor – Castle Project (http://docs.castleproject.org/Windsor.MainPage.ashx)
• Ninject (http://www.ninject.org/)
• StructureMap (http://docs.structuremap.net/)

Thanks in advance for your inputs.

Don’t you ever wonder to print out that whiteboard or have it emailed to you?

We often take photos of the drawing and it makes sense only if the drawing is not too larges.
Not to mention that those pens smell bad often times and they go low in ink etc when you need it most.

Here is a solution (expensive solution though $1000.00+)

Wanna buy? Try this: http://www.fatcatalog.com/pd/34630/electromagnetic-interactive-dual-pen-whiteboard-with-hot-keys-88-diagonal

It is actually not difficult to move your asp.net application to Azure even if you are using Sessions.

This is just because of the services offered by Azure Cache. In the end, you only need to make few changes your web.config and you will be running your session through distributed cache which is provided by Azure Cache.

In simple terms, the following is the only thing you need to do:

<sessionState  mode=”Custom” customProvider=”DistributedSessionProvider”>
<providers>
<add name=”DistributedSessionProvider”
type=”Microsoft.Web.DistributedCache.DistributedCacheSessionStateStoreProvider, Microsoft.Web.DistributedCache”
cacheName=”default” applicationName=”Contoso”
useBlobMode=”true” />
</providers>
</sessionState>

Please read more @ http://msdn.microsoft.com/en-us/library/windowsazure/gg185682

Here are few nice articles about Service Bus on Azure

1. How does it work: http://www.codeproject.com/Articles/276400/Using-Windows-Azure-Service-Bus-Messaging
2. Another how does it work with topics and subscriptions: http://robbincremers.me/2012/02/20/windows-azure-service-bus-messaging-with-publishsubscribe-pattern-using-topics-and-subscriptions/
3. Great tool, Service bu Explorer: http://code.msdn.microsoft.com/windowsazure/Service-Bus-Explorer-f2abca5a

I still can’t believe there is still no support for Azure in Dev 11 / .Net 4.5

There are ways to do so but not nice yet.
I would like to get the bits to publish my .Net 4.5 ASAP!

Building a new tool for personal use which can become commercial later on (so many alternatives already out there in market anyway) where my “My Documents” to be synced with the blob account using sync framework.
I am totally amazed with the amount of work Microsoft did for sync framework, it is really awesome.
Very well done and most problems are just simplified.

Starter blog/code for this is: http://code.msdn.microsoft.com/windowsazure/Synchronizing-Files-to-a14ecf57

Next: Syncing database to SQL Azure using sync framework (I see lots of work done around this only)

Currently working hard to define multiple Career Paths for better and brighter future

• Professional Track
• Developer/Engineer up to Enterprise Architect
• QA up to Lead QA & QA Architect (mutliple subjects)
• Management Track
• from Tech/Team Lead (Developer Engineer) up to Director
• from Lead QA to QA Manager & QA Director

This should have been done long back but fixing the missing link is much more important now than asking why.

Finally SevDer ORM+ had a long way so far and almost ready.
I would like to share the first  preliminary screens.
Tool will be completed by tonight/tomorrow I hope.

Here you just need to select the profile or just start building one.

Very simple profile setup..

Code Generation based on selected Profile (ORM)

Here you go with code generation, ORM kicks the way you need!
As you see even it generates ASCX files (I will in the future add ASPX option and MVC/RAZOR too, but not yet)

After getting frustrated with the fact that Entity Framework and NHibernate does not resolve my needs, I am writing my own ORM tool to finalize one very important part of enterprise architecture.

Here are the features that are included (hope to finish by tomorrow)

1. Mutliple entity classes (one per each)
2. Single Data Provider Class
1. One Interface IDataProvider
2. One Class which inherits I[Model]DataProvider (SQL[Model]DataProvider)
1. [Model] to be renamed by the model name provided
3. One mocked class using moq framework (http://code.google.com/p/moq/)
3. SQL[Model]DataProvider will also implement retry logic in case of certain cases such as
1. Deadlock
2. Connection Timeout etc.
3. In a nutshell the following error codes : -1,-2,2,53,1222,1205
4. Will obviously generate related stored procedures and utilize them
5. Entities will be able to track simultaneous changes and will be able to throw exception if data changed before update!
6. Entities will implement [DataContract] & [DataMember] so that usage in WCF will be a lot easy
7. As you may see from here generated codes will implement Abstract Factory (Provider) design pattern and possibility of Singleton is also there.