Deployment of C# interface based app
Dear All;
We have one issue with one of our superior, he wants an interface which was done in window form application using C# programming language opposed to the MS access interface done with VBA, according to him, VBA is too junior compared to C#. Correct me if I’m wrong:
(1) VBA & C# code are very much similar, the only major notable differences are :
• In C# we use curly blackest ({}) while in VBA they are not applicable
• VBA works only along a program for example Excel, Word or Ms Access while C# work in windows not necessary a program
• VBA uses Subs & Functions while in C# uses Functions
• Variables C# are declared in one standard way while in VBA you opt to use Dim function, for example in C# an integer will be declared like ( int firstNumber ) if we want to store a number we will just now write like ( firstNumber = 12) while in VBA we will use Dim ( intFirstNumber as integer ) and then say intFirstNumber = 12)
Now my question is how we are going to deploy an interface written in C # connecting to MS Access Back End through Sql scripts to our clients.
Currently all our interface are based within Ms Access (FE), we simply tell our client to download Ms Access runtime for all the users and put the Backend on the server while all the users will have their FE installed on their machine.
Any idea how to deploy this C# interface based application to the clients??????????
We have one issue with one of our superior, he wants an interface which was done in window form application using C# programming language opposed to the MS access interface done with VBA, according to him, VBA is too junior compared to C#. Correct me if I’m wrong:
(1) VBA & C# code are very much similar, the only major notable differences are :
• In C# we use curly blackest ({}) while in VBA they are not applicable
• VBA works only along a program for example Excel, Word or Ms Access while C# work in windows not necessary a program
• VBA uses Subs & Functions while in C# uses Functions
• Variables C# are declared in one standard way while in VBA you opt to use Dim function, for example in C# an integer will be declared like ( int firstNumber ) if we want to store a number we will just now write like ( firstNumber = 12) while in VBA we will use Dim ( intFirstNumber as integer ) and then say intFirstNumber = 12)
Now my question is how we are going to deploy an interface written in C # connecting to MS Access Back End through Sql scripts to our clients.
Currently all our interface are based within Ms Access (FE), we simply tell our client to download Ms Access runtime for all the users and put the Backend on the server while all the users will have their FE installed on their machine.
Any idea how to deploy this C# interface based application to the clients??????????
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
But the cost of using Winforms is a steep learning curve and two to three times as much coding - and time, if not more - sometimes even for the simplest things. On the other hand, if you love OOP you really will feel at home in Visual Studio which is a marvelous product.
So, you can choose to take the comment from your superior as a challenge - but it will be a completely different task.