|
OK, how many idfferent ways do you want to be told that piling everything into a monolithic .DLL is doing it the hard way?
|
|
|
|
|
Dave, Mark,
Your last 3 post are useless and lack of technical information. So I suggest not to follow "contributing".
This is a proof of concept. I am not looking for traditional solutions. I know all them.
Maybe you have not understood that this is a suite of highly complex products, with **thousands** of functionalities. Deployment and test cost million of dollars.
Sorry Dave, I have a mess of responses here. My last comment was for Mark.
Best regards,
Jaime.
|
|
|
|
|
Jaime Olivares wrote: a suite of highly complex products, with **thousands** of functionalities. Deployment and test cost million of dollars.
As we have been saying. A huge monolithic deployment is not where you should be focusing, especially, given this information. It costs much more, in money and time, to support a monolithic application. Why do you think this type of application was abandoned long ago.
You break the functionality into smaller pieces so they can be developed and tested separately. Pick up some books on software architecture and design, ones published after the 1980's that is, and read how the rest of the software industry has been progressing, then maybe you can catch up.
Jaime Olivares wrote: I know all them.
Enough said on all of this. You don't seem to want to listen to reason or advise so good luck
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: You break the functionality into smaller pieces so they can be developed and tested separately.
Yes, and that's exactly the problem, when you break them into smaller pieces (dozens), then you have a hell of versions that generate totally unexpected defects (not the folder/dll hell, btw) when trying to communicate one with each other.
Mark Nischalke wrote: Pick up some books on software architecture and design, ones published after the 1980's that is, and read how the rest of the software industry has been progressing, then maybe you can catch up.
Already did that. This just tell me about the main streamline. For this kind of research, academical papers is a better choice, already read some of them too.
Mark Nischalke wrote: Enough said on all of this. You don't seem to want to listen to reason or advise so good luck
I don't want to know about industry trends, because I know them, I have enough books and RSS suscriptions. I am researching for alternatives.
Best regards,
Jaime.
|
|
|
|
|
Is there a way to draw lines , shapes ... in Visual Studio 2005 in design-time ?
|
|
|
|
|
|
|
I build application in vb.net 2005. Now i want to deploy it through setup (build through setup and deployment project in vb.net),
I want to install sql server2005 express with my setup if anyone know, please help me and tell me the complete steps.
|
|
|
|
|
|
Hi All,
i have developed a windows application and i have create the setup for the application. But my problem is how can i add a icon/image in that setup file.for example for sqlserver setup they had their own icon,for VLC player setup they had their own icon..I also want my setup has my own icon.
Plz tell me...
Thanks,
Sk inayat.
|
|
|
|
|
|
thanks for ur post, but it was not working....
|
|
|
|
|
I want something like paper forms that is filled by hand, in my program. The filled form should be stored as a field of type binary in the database. What I need is a framework for making and presenting those forms;for example as a word document...
I want the forms to open without the need for a software(e.g. like word office) . The form should be opened in a .NET windows form and changed there.
|
|
|
|
|
|
InfoPath ?
only two letters away from being an asset
|
|
|
|
|
Whatever name . Just a clean solution. I dont want to engage in its complexities.
The font and layout of the form should be fixed and the user would just type in tables' cells and not be permitted to change the layout. No toolbar for changing fonts and the like is needed just typing should be allowed.
If you are a girl ... then ...
|
|
|
|
|
Another option is to use a PDF library to display the form with edit fields. Of course you can alwasy just create your own windows/web form.
You don't need to store the form in a binary format in the database, only the data that was entered.
devboycpp wrote: Whatever name . Just a clean solution. I dont want to engage in its complexities.
Since we know nothing about your requirements or constraints for the project we can only offer suggestions. It's up to you to determine which is the best method.
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: You don't need to store the form in a binary format in the database, only the data that was entered.
Dude , the reason why I want this is because the fields of the form are many (almost 130 ). The data in fields are all of varchar type. I go crazy having to make a table with 130 fields and a form to show those fields , a stored procedure to update , insert to those fields.
Do you have a more elegant way ?
|
|
|
|
|
Then what happens when the form changes? The previous versions you have stored are all invalid?
A more elegant solution would allow the data to be stored independent of the presentation.
I'm sure this data could also be used for analysis also, forming charts or graphs. It wouldn't be possible in a binary format.
devboycpp wrote: The data in fields are all of varchar type.
Are the fields truely all varchar, or are you being lazy and making them such? What about validation of the data entered?
If they are all truely varchar then a table could be constructed with a name/value pair. With an identity column, that's only three columns. Is that too much for you?
If they are not all varchar and you need to create a table with seperate columns, using Linq to SQL or Entity Framework you can eliminate the need to write and maitain stored procs. Also, I'm sure there is potenttial to normalize the data and elimiate some of the columns.
Lastly, don't call me dude.
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: Lastly, don't call me dude.
Is it insult to call someone dude or what ?
If you are a girl ... then ...
|
|
|
|
|
To me, yes
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: If they are all truely varchar then a table could be constructed with a name/value pair. With an identity column, that's only three columns. Is that too much for you?
With this solution when creating a form for the first time we have to insert 130 records into the table and when updating likewise. I don't know how much it will affect the performance.
And also when fetching data it is not straightforward to display data in the form.
If you are a girl ... then ...
|
|
|
|
|
devboycpp wrote: we have to insert 130 records into the table...much it will affect the performance.
You can't be serious? Modern databases, such as SQL Server, can handle thousands of transactions per second. Do you really think 130 rows is going to cripple it?
devboycpp wrote: And also when fetching data it is not straightforward to display data in the form.
form["field name"] = row["field name"].value
Something like this is too cumbersome for you?
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: form["field name"] = row["field name"].value
For displaying data we need to fetch the records into a DataTable. It will contain 130 records . To display the values for the form fields we need to locate in DataTable to find the desired record matching the form entry. Which is not like you said . The above code is for when all 130 fields are stored in one record of a table.
If you are a girl ... then ...
|
|
|
|
|
Notice the Something like this statement. Can you use a little imagination or would you like me to write the application for you?
You've gotten all the help you need. I'll expect either a check or a thank you.
only two letters away from being an asset
|
|
|
|