I'll be talking about all things Rails, Python, Ruby and Java among other topics in this blog. I also enjoy a bit of system programming, so my fun with WebOS, Win32 and Solaris may show up here too.
Interesting technology
Get link
Facebook
X
Pinterest
Email
Other Apps
Found an interesting project called vertx.x I might end up trying to port it to the CLR using the technology that the folks over at the mono-project used for porting android's java layer to C#
I am back, with my usual mono antics! RIM recently had a conference and showed off more of BB10. I have decided I will attempt (albiet in my spare time) to use C# to create a Cascade application. I have a few ideas how i'll accomplish this. I'll post more info as time goes on.
I have been using Linq To SQL in a project recently. Linq is a great way to traverse through a collection of objects. Its a very nice utility and can get rid of those unsightly nested foreach loops with if/elses in your code. Linq To SQL is also a nice basic Object Relational Mapper. The issue is "when the rubber meets the road", as it were. Linq seems a slight bit incomplete. Take this example: A simple ChangeLog class. It has an Enum ChangeLogStates that has 4 states, Created, Modified, StatusChanged (a disposition), Shelved(basically deleted). Now, i could do an ChangeLog.add(LogStates.Created/Modified/Changed/Shelved,Object Key, strDescription) to every line of code where there is a change in the database....everywhere i insert, update the underlying entity. But Using the beauty of OOP and Linq to SQL, i can impletement the Datacontext's insert and update partial methods: partial void insertLinqItem(LinqItem item); partial void updateLinqItem(LinqItem item); in...
Just a note. Azure App services do not directly support 64bit dotnet core applications. https://blogs.msdn.microsoft.com/webdev/2018/01/09/64-bit-asp-net-core-on-azure-app-service/
Comments