This is just a place to put things I have found for my own future reference, and for anyone else who happens to stumble across it.
When creating a mock of a Database Table, it is helpful to have some pre-existing data rather than creating it all from scratch. This can be accomplished by outputting the current content of a table to XML, then using this XML as the data source to test against. To get hold of the data, in …
The problem I have an application that is using Entity Framework to connect to the underlying SQL database. A number of these tables allow items to be updated, but not all of them. Each of the tables that can be updated have the following properties dbo.Delivery Columns Id (PK, int, not null) Project_Id (FK, int, …
After playing around this evening by following this Channel 9 tutorial – I got the following up and running. If you’re interested, you should say hello, or ask about the weather in a place, or ask about “jonnus” I intend to progress this further following information at this link
I currently work for Mouser Electronics, as part of the Internet Business team. This website is primarily written C# 5.0 using the .NET framework. I am on the team reworking this legacy website to take advantage of the benefits we can gain from adopting MVC5 to this solution. I am also leading the way in taking advantage of this situation to adopt a culture of performing Unit Testing to provide improve our ongoing reliability and to improve regression testing.
Recent projects have included
- Reworking the Account Creation process
- Providing support for our partners at Macnica in Japan
- Ongoing conversion of legacy Active Server Pages to MVC views