Popular programmatically x data manually

Question

Popular programmatically x data manually

Asked 10 years, 9 months ago

Viewed 241 times

4

You can popular one-component data on .NET using Visual Studio interface (Select Datasource...).

From the point of view of popular performance data via code is faster than manualmentr?

3

I think you mean "engage" instead of "copulate," no?

– Oralista de Sistemas

2014/03/24 at 11:59
Or maybe, more likely, "popular" data? hahaha

– Luiz Vieira

2014/03/24 at 12:02
1

@Luizvieira Corrected, I always get confused! Thank you.

– Laerte

2014/03/24 at 12:12
@Laerte No mistake. At least guaranteed a good laugh right? : ) Ah, failed to correct in the body of the text.

– Luiz Vieira

2014/03/24 at 12:32
1

@Luizvieira Corrigi! What matters is to learn, to err is part of the process! Thanks!

– Laerte

2014/03/24 at 12:35
1

Yeah, unless the question is about genetic algorithms, I think data copulation doesn’t make much sense... D

– mgibsonbr

2014/03/24 at 15:32

Show 1 more comment

2 answers

2

There must be no difference. What Visual Studio does when you select a Datasource through its graphical interface is to generate the association code automatically. You could write that code yourself. There will only be a difference in performance if you are assembling your Datasource manually and in some inefficient way.

If you expect the database to change, it is best to abstract as much of the Datasource construction as possible. It is preferable to also leave the connection data in a configuration file in that case. Or somewhere else where you can easily change this data without having to recompile the program.

Browser other questions tagged c# visual-studio

You are not signed in. Login or sign up in order to post.

by Tafarel Chicotti • **2,715** points · Answer 1 · 2014-03-24T12:08:16+00:00

Laerte, when you populate your Dropdown via code, you win in the matter of abstraction, because you can decouple the business rule coming from the bank through Datasource.

For example, if you have an application today in an SQL Server database and tomorrow discover that you need to migrate the database to an Oracle and not mess with its table structure, if you popular for Datasource all your Dropdowns, when you migrate, You’ll have to redo them on hand to use another Egg. If you do it via code, with a well-structured and separate architecture and using a generic data access layer, you hardly have to mess with your code, depending even for example on ORM you use, maybe you just need to change the connection path of the database.