Comments for adam mokan

Comment on Looking for feedback on future content by Rob Jones

Rob Jones — Wed, 09 Nov 2011 16:19:17 +0000

I would love to discuss a direct hire full time opening I have with you. Please give me a call 602.273.7100

Rob

Comment on NuGet.Server sample project by adam.mokan

adam.mokan — Thu, 03 Nov 2011 01:28:15 +0000

I’m actually running this on IIS 7.5 on Win Server 2008R2. I used the same approach, minus some of the config hacks I had to make for IIS Express. The main difference, for me on Windows Server, is that I have a CNAME setup and a unique site dedicated to NuGet.

Comment on NuGet.Server sample project by Anthony Mastrean

Anthony Mastrean — Thu, 13 Oct 2011 20:33:06 +0000

I was trying to startup a NuGet Gallery on full IIS, a bit different. And I figured it out, kinda

[1]: https://github.com/NuGet/NuGetGallery
[2]: http://anthonymastrean.tumblr.com/post/11405529860/getting-a-nuget-gallery-running

Comment on Removing a corrupt Project Collection in TFS2010 by Carlos

Carlos — Wed, 27 Jul 2011 21:29:38 +0000

I had a similar issue and the above solution worked for me too.

Thank you!

Comment on node.js running in a Windows Azure Worker Role by Hernan Garcia

Hernan Garcia — Tue, 26 Jul 2011 13:38:44 +0000

FYI: npm doesn’t work yet, since spawn child_process is not done for windows. There is an alternative ryppi (https://github.com/japj/ryppi). It’s a python base package module for now.
Express works fine, as well as the ejs templates (not sure on complex scenarios since I was only able to do some basic testing).
If you don’t want to use ryppi you can always install modules manually. You will have to open each package.json and install dependencies as well.
Great post!

Comment on Looking for feedback on future content by adam.mokan

adam.mokan — Mon, 18 Jul 2011 22:47:16 +0000

Sounds like #1 is going to take the win in a landslide at this rate.

I will plan on splitting it up in a multi-part and maybe just walkthrough the basics of handling repositories with EF 4.1 and MVC3 without getting all “academic” like most info I run into does. But in the first part I will at least cover my generic repository implementation, scaffolding, and the lifecycle of the DbContext with a touch on the EntityFrameworkProfiler tool. After that initial post, I will go over the unit testing aspect using the same repository along with SQL Compact and NBuilder, to generate fake data, for testing.

My goal is to keep it as simple as possible, yet flexible enough to scale and be used in high transaction environments.

Comment on Looking for feedback on future content by Michael Duddles

Michael Duddles — Mon, 18 Jul 2011 21:04:52 +0000

Hi, Adam. We met at Desert Code in April. Your helpful attitude really stood out there, so much thanks. (I’m back living in Chicago now, btw).

Though these are all interesting topics, I’m going to give a vote for the first one on listed: Detailed post on generic repository pattern for MVC 3. The more detail the better…

-Mike

Comment on Looking for feedback on future content by Roger Stepper

Roger Stepper — Mon, 18 Jul 2011 20:00:42 +0000

I would like either the first or last choice. I have seen some of the MVC3, EF 4.1 with DI and seeding data, but a more complete code sample would be good. TeamCity in the cloud also interests me.

Comment on Looking for feedback on future content by aendenne

aendenne — Mon, 18 Jul 2011 19:31:24 +0000

I’d like number one to be the item at top (generic repo pattern for MVC 3 & EF 4.1) and the other item that stands out/interests me is the HTML Helpers post. I don’t blame you for not getting to them though. My blog is bleak. So much code, so little time…………

Comment on Co-admin weirdness in the Windows Azure dashboard by adam.mokan

adam.mokan — Mon, 18 Jul 2011 19:02:02 +0000

Thanks for the comment. At least I’m not the only one that is confused!

I really do like Azure and see lots of future potential. However, they need to take a lesson from Amazon in some ways. Amazon has a consistent dashboard, although it’s not perfect. Right now, with the various Azure CTP’s and special CTP dashboards (I’m looking at you Sync Services) make it feel like a patchwork admin system where there is a lack of internal communication between the various teams. Having said that, the big upside to Azure, from my point of view, is that it is more “developer friendly” (at least for the .NET folks) and for those looking to dip their toes in the cloud. With Amazon, OS-level knowledge (security, firewalls, patching) is paramount. Azure allows a developer to just deploy and not worry about OS details, unless needed.