Monthly Archives: August 2014
I was looking at an issue posted in the forum about not able to debug server controller for admin extension. Couldn’t really figure out what could be the root cause, as the controller should get loaded and return data (default expectation). Getting a 404, strange.
Looked at the issue over a remote session and we found the root cause of the issue from event log.
LogName: Microsoft-WindowsAzurePack-MgmtSvc-AdminSite/Operational Error:Unhandled exception: FileLoadException: Could not load file or assembly 'System.Web.Mvc, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
For some reason, the NuGet package on the development environment updated the project to MVC 5.2 and the WAP Admin site was not loading the extension DLL because of the failed dependency.
Thought others might also run into this issue (knowingly or unknowingly) . As a quick resolution, we rebuilt the admin extension against MVC 4.x libraries and it started working.
Made some good progress on the 0.1 version of storage sample. Except for some basic code clean up (which I am planning to take up along with v0.4), it is all good. You can browse / download the sample code from Git Project. Providing the screen captures, so that everyone can easily have an expectation on the feature set of v0.1.
If you have any questions on the code sample, need help with some specific scenarios, you can reach me through MSDN forum for WAP. I follow the forum almost daily.
If you would like to see what is coming next, check out this blog page.
I was looking at various resource provider implementation (Hello World and other content script files with in the deployment) to understand various approaches, in addition to the resources available on MSDN. Now, I am in a good state to start the development of storage sample for Windows Azure Pack. I am thinking of following as the various features for the sample.
- 0.1 – Basic sample with minimal capabilities (with in-memory data provider)
- Admin should be able to create storage locations and map it to physical network location
- Tenant should be able to create containers with in specific locations
- Tenant should be able to delete container
- 0.2 – Tenant should be able to upload files to container
- Note: No plans to support folders with in a container
- 0.3 – WAP Drive
- A stand alone web application to interact directly with Tenant API and demonstrate a photo album
- 0.4 – Stabilize
- Clean up code, comments added as required.
- Refactor API library with clean web-api implementation
- 0.5 – Implement usage
- 0.6 – Implement quota
- 0.7 – Implement database data provider with updates to setup
- 0.8 – Implement custom PowerShell commands to enable tenant operations
Mostly I plan to get one minor version made available every week with v0.1 to be made available around 8/17/2014.