Explore >> Select a destination
|
You are here 
|
www.mashitup.be | ||
| | | | |
alesruzicka.net
|
|
| | | | | English articles from Ales Ruzicka, software developer and lecturer | |
| | | | |
alesruzicka.eu
|
|
| | | | | English articles from Ales Ruzicka, software developer and lecturer | |
| | | | |
jackhiston.com
|
|
| | | | | Programmers are lazy. We love tools that automate our lives. Why not automate data? A time-consuming but necessary part of a programmers job is seeding data into a database. Demonstrations, load performance, styling, testing, all need a way to generate data. A rudimentary way of doing this is by hand. Spending days, sometimes weeks, inputting data into a system until it represents a realistic go-live scenario. Once you begin to realise doing it by hand is inefficient, you decide to create a seeding application that does it for you. | |
| | | | |
www.jimmybogard.com
|
|
| | | Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the previous post, we looked at techniques for determining the size and scope of our .NET migration effort, as well | ||
