Re: Home VS Pro version design help - C# Discussion Boards

Re: SQL Server Connection with C# program

23-Jul-07 20:05

Sounds like some kind of user privilege problem. Does it work if you are not using Windows Authentication?

"The clue train passed his station without stopping." - John Simmons / outlaw programmer

unitecsoft25-Jul-07 3:51

unitecsoft

25-Jul-07 3:51

I Don't think its a user privilege problem , no reason to have a successful connection in the first run then a failure connection in the second run while no changes in anything between the two runs . could it be a setup parameters problem for the .NET framework or SQL server .
I will try to change windows Authentication to sqlserver security .

UnitecSoft

We will Either Find A Way Or Make One .

Re: SQL Server Connection with C# program

unitecsoft5-Aug-07 2:14

unitecsoft

5-Aug-07 2:14

hi everyone

Just to share the information , The reson of being unable to connect to sql server database via C# application was due to the anti virus protection I am useing ( Kaspersky ) . Disabling this program will solve the problem . maybe there is a certain setting within Kaspersky to allow or deny this access . Big Grin | :-D

UnitecSoft

We will Either Find A Way Or Make One .

Home VS Pro version design help

student_rhr23-Jul-07 13:15

student_rhr

23-Jul-07 13:15

I am working on an app which will have three version named Home (free), Pro (very little cost), Corporate (costly).

What is the best approach to accomplish this task?
1- Should I make three different Projects and apply necessary settings accordingly?
2- Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed?
3- Should I make just one project and use the product key to distinguish which version was installed?
3- Other technique...

I would appreciate your help and advice. Thanks.

Luc Pattyn23-Jul-07 13:36

Luc Pattyn

23-Jul-07 13:36

Hi,

if you trust the licensing key or copy protection mechanism sufficiently to protect
the expensive version, I see no point (other than maybe size, or time to market) to
create trimmed versions; just let the license stuff control which parts are functional
and which are not.

That basically is what Microsoft did when they launched XP Home and XP Pro.
Dont know about Vista.

Hope this helps.

Luc Pattyn

try { [Search CP Articles] [Search CP Forums] [Forum Guidelines] [My Articles] }
catch { [Google] }

Christian Graus23-Jul-07 13:44

Christian Graus

23-Jul-07 13:44

IMO, the best approach is to put the pro only and corporate only functionality in dlls, which are dynamically loaded. That way you have one version, but you never ship people code that they are not allowed to use ( givn that they can decompile your code to remove any blocks that you put in there )

Christian Graus - Microsoft MVP - C++

"I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

Paul Conrad23-Jul-07 13:56

23-Jul-07 13:56

student_rhr wrote:
1- Should I make three different Projects and apply necessary settings accordingly?

That is a bit of redundancy.

student_rhr wrote:
Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed?

You could, but you may run into versioning nightmares.

student_rhr wrote:

3- Should I make just one project and use the product key to distinguish which version was installed?

You could, but someone could look into the code and try to hack a workaround.

"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus

student_rhr24-Jul-07 6:15

student_rhr

24-Jul-07 6:15

What is the best industry practice?

Paul Conrad24-Jul-07 6:19

Call .Net 2005 DLL in .Net 2003

24-Jul-07 6:19

I am not 100% sure. It is something that does vary from software shop to software shop.

"The clue train passed his station without stopping." - John Simmons / outlaw programmer

Bhavik Solanki23-Jul-07 12:00

23-Jul-07 12:00

Hi Friends,

I need help. I have C#.Net 2005 DLL(COM Introp), and I want to use/call it in VB.Net 2003.

I have tried various posibillites but it doesnt work. Following are some of them.
1) Give project reference (Not allowed)
2) Add reference (Not allowed)

Is anybody help me how to do that?

Thanks in Advance

originSH23-Jul-07 12:06

originSH

23-Jul-07 12:06

Why would you want to use it in 1.1 when you could code it in 2.0 and have all the advantages of the extra features and better IDE?

You'll need to install the .Net 2.0 framework anyway so why not just use that?

Bhavik Solanki23-Jul-07 12:20

23-Jul-07 12:20

I have some applications which is already developed in Framework 1.1 and as of now its not posible to move to Framework 2.0.

Paul Conrad23-Jul-07 15:14

23-Jul-07 15:14

Bhavik Solanki wrote:
which is already developed in Framework 1.1 and as of now its not posible to move to Framework 2.0.

Have you tried running the solution from 1.1 through the converter to make it 2.0?

"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus

Scott Dorman23-Jul-07 14:17

Scott Dorman

23-Jul-07 14:17

The simple answer is you can't. C# 2.0 (from VS 2005) uses .NET 2.0 while VB.NET 2003 uses .NET 1.1. These are different runtimes and are not compatible with each other. Beyond that, you can't have one application that loads two different versions of the runtime.

-----------------------------
In just two days, tomorrow will be yesterday.

http://geekswithblogs.net/sdorman

Bhavik Solanki23-Jul-07 14:39

23-Jul-07 14:39

Thanks for reply

Here is some more info on this topic : http://www.thescripts.com/forum/thread661371.html[^]

Thanks Again

originSH23-Jul-07 22:18

originSH

23-Jul-07 22:18

As a hack you could load it as an out of process COM server, but it's bad and wrong, just upgrade the damn app already :P it'll be worth it in the long run. There were very few breaking changes between 1.1 and 2.0 so theres not much excuse for not upgrading.

Bhavik Solanki24-Jul-07 12:22

C# choosing database connection

24-Jul-07 12:22

Thanks to All of you.

After doing lot of R&D and Spending lot of time on it, finally I come to the decision that I will upgrade existing applications to Framework 2.0. Frown | :(

Thanks Again.

lino_i23-Jul-07 8:47

lino_i

23-Jul-07 8:47

I have a GUI utility and it connects to a sql server 2005 database. All of the connection code has been generated by the IDE.

I have 2 databases one for produciton and one for development. How can I switch the connection string? I am currently doing it in the Settings.Designer.cs file and checking for

#if DEBUG
//use the dev server
#else
//use the prod server
#endif

however everytime i alter the settings.settings file the IDE rewrites the Settings.Designer.cs file.

this is how the code currently works:

currently when i start my application the connection string is initialized like this:
this is called:
internal System.Data.SqlClient.SqlConnection Connection {
get {
if ((this._connection == null)) {
this.InitConnection();
}
return this._connection;
}
which calls this:
private void InitConnection() {
this._connection = new System.Data.SqlClient.SqlConnection();
this._connection.ConnectionString = global::DGView2.Properties.Settings.Default.ProdConnectionString;
}
which calls this:
public string ProdConnectionString {
get {
return ((string)(this["ProdConnectionString "]));
}
}

app.config file:

<connectionStrings>
<add name="DGView2.Properties.Settings.ProdConnectionString"
connectionString="Data Source=localhost;Initial Catalog=MyDatabase;Integrated Security=True"
providerName="System.Data.SqlClient"
<add name="DGView2.Properties.Settings.DevConnectionString" connectionString="Data Source=localhost\DEV;Initial Catalog=MyDatabase;Integrated Security=True" />

</connectionStrings>

I guess part of the problem is that this line of code:

this._connection.ConnectionString = global::DGView2.Properties.Settings.Default.ProdConnectionString;

is always calling: public string ProdConnectionString

so in my Settings.Designer.cs file I have set it up this way:

public string ProdConnectionString {
#if DEBUG
get { return ((string)(this["DevConnectionString"]));}
#else
get { return ((string)(this["ProdConnectionString"]));}
#endif
}

I am not convinced that this is the best way to do it. The ideal situation I think would be to use the desired property based on DEBUG or RELEASE in the call to the connection string:

#if DEBUG
this._connection.ConnectionString = global::DGView2.Properties.Settings.Default.DevConnectionString;
#else
this._connection.ConnectionString = global::DGView2.Properties.Settings.Default.ProdConnectionString;

#endif

however there are just to many instances of this therefore making it less efficient.

any suggestions?

thx

Paul Conrad23-Jul-07 8:51

23-Jul-07 8:51

You may need to look in the App.Config file...

"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus

lino_i23-Jul-07 9:09

lino_i

23-Jul-07 9:09

i am looking in the app.config file that's where the settings are stored...that's not the problem

thx for your help tho

Pete O'Hanlon23-Jul-07 9:29

Pete O'Hanlon

23-Jul-07 9:29

The normal way of doing this is to just use one setting. You change the config file, so that you have a debug version and a release version.

Deja View - the feeling that you've seen this post before.

Vikram A Punathambekar23-Jul-07 17:10

Vikram A Punathambekar

23-Jul-07 17:10

I second what Pete said - use one setting, called ConnectionString and edit the file depending on whether you want it to work on Dev or Prod.

Cheers,
Vıkram.

After all is said and done, much is said and little is done.