I am kinda new in C# so i just create a simple aplication using a database.......you know insert Update..delete.......but what other thing can I try ???
any idea........please remenber I am a rookie >_<
I am kinda new in C# so i just create a simple aplication using a database.......you know insert Update..delete.......but what other thing can I try ???
any idea........please remenber I am a rookie >_<
Nice first step, — building CRUD shows you understand the basics. Replies from , and point in useful directions. Below is a compact, practical plan that turns a simple database app into a learning project that teaches architecture, security, testing and deployment.
Pick a single, real-world problem you care about (for example: a personal expense tracker or a tiny inventory system). Deliver it in small increments: design a normalized schema, build forms for create/read/update/delete, then add one feature at a time that forces you to learn a new concept — file import/export, aggregated reports, search and pagination, scheduled jobs for recurring items, or simple role-based access. Each new feature gives you concrete goals: indexing for performance, SQL for reporting, or parsing CSV for imports.
On the technical side, practice layering and separation of concerns: presentation, business rules, and data access. Try both raw ADO.NET and an ORM (Entity Framework or a micro-ORM) so you see tradeoffs. Add authentication (use the framework identity tools rather than rolling your own), parameterize all queries, implement transactions for multi-step updates, and add logging plus basic unit tests for business logic. Use a local dev database, migrations/schema versioning, and Git for source control.
Troubleshooting tips: seed the dev DB with realistic data; profile slow queries and add indexes where needed; reproduce bugs with unit/integration tests; never store passwords in plain text; close/dispose connections properly. Start small, ship a working feature, then iterate. That steady expansion teaches far more than jumping between unrelated sample apps.
Jump to Post— Ramy Mahrous 401Multiuser phone book, it's nice :) I developed it when I was C# beginner.
Jump to Post— Ramy Mahrous 401As you like, but I used MS SQL Server 2000
Multiuser phone book, it's nice :) I developed it when I was C# beginner.
a phone book.......yeah. could be
whta did you used to save the phones, adress, names?? SQL or another DB
As you like, but I used MS SQL Server 2000
any app which gets your imagination going and you can keep building on for a while is a good app. You sound like you want a database challenge so, start with a simple db+client and then work to a 3 teir approach and get into those kinds of aspects.
Write an application that makes coffee ... hahaha, i'd buy that twice !!!
How about you send me a msg man , like to give you some ideas...
Maybe you could help me with some of my test dummy applications (like my new one , i am trying to write a self learning application...)
Well, my "test" app is an RPG game a bit like a muck, so Im recreating an evironment I know well but I can extend it to the point of writing my own programming language with in it, multi user, networks, reports, db, I can make it as much or as little as I want.
The key part is to find something interesting - another one of mine is a "things to do " program, where you schedule things, or just have "stuff" you need to do, priorities, sorting, different class types for different "things" you're doing, eg, maybe a holiday which has a start and end, or just something you want to work on.. so has no start, no end, but is "on going".. it may have sub parts, some compulsary, some not..
or it could be a game like my RPG game.. it just needs to be something that you're interested, that you'd use, if you wouldnt use it, its pointless.
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.