|
mAzeem22 wrote: i want to know is Matlab suitable for OCR or C# is best for OCR ?
Completely irrelevant because you have already made a platform decision and had you done any research at all, you'd know that MatLab does not run on Android.
mAzeem22 wrote: or can we convert the C# program is Android Application ?
Again, a quick search on the internet would have found the answer. Yes, you can run a Mono version - there's one from a company called Xamarin called MonoDroid, but it probably has big limitations as far as you are concerned - it's not free.
|
|
|
|
|
Is there anyone here experience with both C# and VB?
I am a C# developer. I am about to modify a Visual Basic project. All the documents are provided. I personally not interested in taking up a VB project.
Apart from my interest, is there any worth doing VB projects these days. Cons and Pros please?
thank you
Swinkaran
|
|
|
|
|
VB is just another language, another tool you can put in your box. Getting the hang of VB syntax while irritating after C# will be fairly easy. It was going the other way!
If you are not interested in doing the project then why ask if you should. If you have a choice as to whether you do the project why don't you have the choice of language, seems odd to me.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Looks like your team / management has already decided they want to use VB.
There is no point discussing pros and cons if you don't have a choice.
|
|
|
|
|
Abhinav S wrote: There is no point discussing pros and cons if you don't have a choice.
Hi Abhinav, the point is: he does have a choice which is to "pass on" the project.
He did not ask the question: "will I be able to work in C#, using the VB Project, as is, as a base ?"
And, we have no information from the OP here about what the project is, if there is a team involved, etc.
So, I find your answer rather strange 
best, Bill
"Takuan Sōhō died in Edo (present-day Tokyo) in December of 1645. At the moment before his death, Takuan painted the Chinese character 'meng' ("dream"), laid down his brush and died."
|
|
|
|
|
This projected was passed onto my desk, but with the question "Do you want to take over this VB project?"
well, I still have the option to pass this project to another desk.
Getting to know VB is not a bad think,, of course it is an additional knowledge. The scope for VB in Australia is not in demand.
I will update the final decision in another 24 hours.
thanks guys.
|
|
|
|
|
We know from your second comment that you don't wish to do this.
So, the question becomes a "cost/benefit" analysis:
1. does taking this on this VB project increase your status (and, perhaps future evaluation, and pay, or being considered for another, more senior, position) in any tangible way ?
2. does taking the "option to pass this project to another desk" you have: have any negative effect on your career in the company ?
3. do you even care about your future status, or career, in this company ?
4. is VB experience going to make you more "marketable" as a programmer outside the company in the future ?
"Takuan Sōhō died in Edo (present-day Tokyo) in December of 1645. At the moment before his death, Takuan painted the Chinese character 'meng' ("dream"), laid down his brush and died."
|
|
|
|
|
A basic question to ask is: Do you want to continue in your company, and have a bright(er) future there? If so, you need to take up that project, and do what the company asks you to do; after all, they are paying your salary, right? If you are on your own, then you can dictate what you want to do; but that becomes difficult when you are employed somewhere.
As someone says, VB is not a bad thing - nowadays, you can pretty much do the same things in VB and C# (I mean VB.Net, and not VB6.0); just with a different syntax. So, if you know VB, you know one more way of writing Windows programs in addition to doing it the C# way.
|
|
|
|
|
Amarnath S wrote: A basic question to ask is: Do you want to continue in your company, and have a bright(er) future there? If so, you need to take up that project, and do what the company asks you to do
Hi, Amarnath,
In this scenario, all we know is that the OP has been given the option to take on a VB project: he has not been "assigned" to take on the project. We have no information from the OP about how his decision to take-on or "pass on" this project will affect his future status in this company.
For all we know, he may not care about his future status in this company.
So the effect of his deciding to take on the project, or not, in terms of his future status in the company is something we can only speculate about.
He has told us, in his second post, he does not want to go into VB, and that VB is not in-demand where he is. So your idea that VB is, for this OP, an inherently good investment is, imho, questionable. Going deeply into IOS, or HTML5+JavaScript+jQuery might well be much better investments in his future marketable skills.
In conclusion: I think your comments were may have been a slightly "rush to judgement:" premature extrapolation not supported by what we actually know about this specific scenario.
best, Bill
"Takuan Sōhō died in Edo (present-day Tokyo) in December of 1645. At the moment before his death, Takuan painted the Chinese character 'meng' ("dream"), laid down his brush and died."
modified 26-Sep-12 12:46pm.
|
|
|
|
|
Yes - there are many points to consider before taking a final decision; and the future in his company is also one factor.
I agree with you, not fully though with the "rush to judgement" part.
|
|
|
|
|
Let me ask you this question - My group has WPF application, we use three custom built libraries in this WPF application. These libraries are built as separate projects and have their own Subversion repositories. (4 Subversion repositories altogether)
Question - Should we be using the .dll files in our WPF solution or should we be using the projects from Subversion? and bring the entire project into Visual Studio?
Keep in mind our WPF application isn't the only application that uses these 3 libraries, we have other solutions that use these libraries. We are bringing in the library projects because we frequently modify these libraries when working on our WPF app.
***Here is my concern - we are now moving to TFS from Subversion and TFS has, whats called, TFS projects. Should we be creating 4 different TFS projects, one for each Subversion repository or should we be putting all projects into one TFS project? In TFS you have to create work items for each TFS project so if we have a user story that might need modification of both the WPF app and a library, if the library is its own TFS project, then we will have to create work items in 2 different TFS projects. And that seems redundant/annoying/not efficient.
|
|
|
|
|
As with many things, it depends...
We do the same thing a lot where I work. Sometimes we reference a DLL, sometimes we share the project, sometimes we copy the project and reverse integrate the changes.
Referencing a DLL is the safest answer. You always know what version you are running against and upgrade it when you decide to (Test can run full test passes and make sure nothing broke by doing so).
Sharing a project is very dangerous and is rarely used. If you change an interface in project B, project A probably will no longer compile.
Making a copy of the project and reverse integrating changes is one of the best solutions. It allows bugs to be fixed from both sides of the project and each side gets to decide whether or not to integrate those fixes. This even has the added benefit of allowing you to heavily modify some things (Interfaces, Classes ect) that would otherwise break the other project while still being able to take some bug fix type integration back.
I'm getting tired so hopefully that makes sense.
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
|
|
|
|
|
"Sharing a project is very dangerous and is rarely used. If you change an interface in project B, project A probably will no longer compile."
you shouldn't be changing anything from interfaces (adding stuff is ok). Isn't that what the purpose of an interface is???
|
|
|
|
|
It is. It was meant to serve as an example, albeit a bad one.
Changing a hash function is something I have seen done in this scenario. The havoc this wreaks is... absolutely terrible. I don't even want to get into the details but knowing that this was the cause of the problem, FROM ANOTHER FREAKING PROJECT was angering to say the least.
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
|
|
|
|
|
Ok understood. Does anyone know, or can tell me how a project in TFS is structured? Do I create and put VS projects (dll, WPF, asp, etc) in a single TFS project and seperate them by folders? Or should I map a one-to-one with 1 Visual Studio project (ex. WPF) to one TFS project?
In my TFS book it shows "product families" as a folder in a TFS project. I assume this means a VS project???
|
|
|
|
|
A TFS project is not analogous to anything in Visual Studio. It is more for permissions and work item types.
For most people/teams they will work out of the same TFS Project. I've never strayed out of my TFS Project. We just have different folders for each Visual Studio Project. External teams have a different folder for their team still within our same TFS Project.
The only time I've seen people use other TFS Projects is when they have a different permission model, or different work item types they are tracking against.
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
|
|
|
|
|
OH! so you just keep one TFS project for all your applications? And separate them by folder in your TFS project.
Does everyone agree with this?
|
|
|
|
|
Reference the unless you plan to modify any of the projects.
|
|
|
|
|
chuckdawit wrote: Keep in mind our WPF application isn't the only application that uses these 3 libraries, we have other solutions that use these libraries.
I think this here is what defines it. If these projects are used by more than just one solution, it is usually a good idea to keep them independent.
As for your TFS question, I think the other option you are missing is creating 1 independent Team Project for all these libraries so as for them to remain completely independent from the projects that are using them. As always the devil is in the details and it will depend, among other things, in how these libraries are connected to one another.
|
|
|
|
|
Why is it so in c#
modified 20-Sep-12 23:04pm.
|
|
|
|
|
What does any of this have to do with C#? 
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
|
|
|
|
|
|
Because it's a huge pain in the ass the keep straight!
|
|
|
|
|
Well said, and I live quite happily without it 
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Because many programmers or software engineers are overwhelmed even by single inheritance. Most classes with multiple inheritance in C++ I saw, were badly designed. But you can implement as many interfaces as you like. Try it, count them and give feedback 
------------------------------
Author of Primary ROleplaying SysTem
How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
