05-06-2013, 03:24 PM
Hello,
Regarding Tekla & C#
When I write interaction with tekla I first write a class to hold the logic and objects.
The class is part of a windows form project.
I add reference to tekla dll's as it is written in tekla api help.
After I write the whole logic and test it.
If all works well I can move forward and convert my class into a connection or macro like in tekla api help/samples.
There's nothing interesting about this or nice or .... Just work.
What you wrote in Post: #7 that text from a forum is the contents of a *.inp file.
There's no logic in it because it simply defines attributes for connections or whatever.
It is not C# code or syntax.
To learn c#, download and install visual studio express from microsoft.
Follow these tutorials:
For a non programmer things look like this:
You start with some tools.
On top of them you build your own tool.
Your tool will be written in a language which the computer understands.
In order to write the tool you have to understand first the problem the solution and the way to implement the solution on a computer with a programming language in a windows or not environment.
Programming by itself will not provide a solution but will create a lot more problems.
Each of the new problems related to how to add numbers or how to use forms and buttons (input and output) has to be treated at a time.
Anyway start learning c# by doing things with it, solving something, programming can't be learned like history.
You might be seeing some results after a few months it mostly depends on previous programming experience.
I don't believe tekla is written in .NET because all binary files are not .NET, except for add ons.
The exe has dependency msvcp100.dll, msvcr100.dll, mfc100.dll and other alike.
I don't see dependence of mscoree.dll which is for .NET apps.
It has shw32.dll which is SmartHeap memory management. And the api is just a wrapper. It is true that they used a lot of .Net for macros, plugins and other.
If all the binary and dll files I looked at are encrypted (not obfuscated) and decrypted, JIT ed in ram at runtime it is possible to be fooled by it's protection, I don't think that's true so until someone will provide strong evidence Tekla for me is written in c++. Not that it actually matters.
Regarding Tekla & C#
When I write interaction with tekla I first write a class to hold the logic and objects.
The class is part of a windows form project.
I add reference to tekla dll's as it is written in tekla api help.
After I write the whole logic and test it.
If all works well I can move forward and convert my class into a connection or macro like in tekla api help/samples.
There's nothing interesting about this or nice or .... Just work.
What you wrote in Post: #7 that text from a forum is the contents of a *.inp file.
There's no logic in it because it simply defines attributes for connections or whatever.
It is not C# code or syntax.
To learn c#, download and install visual studio express from microsoft.
Follow these tutorials:
Code:
***************************************
Content of this section is hidden, You must be registered and activate your account to see this content. See this link to read how you can remove this limitation:
http://forum.civilea.com/thread-27464.html
***************************************
For a non programmer things look like this:
You start with some tools.
On top of them you build your own tool.
Your tool will be written in a language which the computer understands.
In order to write the tool you have to understand first the problem the solution and the way to implement the solution on a computer with a programming language in a windows or not environment.
Programming by itself will not provide a solution but will create a lot more problems.
Each of the new problems related to how to add numbers or how to use forms and buttons (input and output) has to be treated at a time.
Anyway start learning c# by doing things with it, solving something, programming can't be learned like history.
You might be seeing some results after a few months it mostly depends on previous programming experience.
I don't believe tekla is written in .NET because all binary files are not .NET, except for add ons.
The exe has dependency msvcp100.dll, msvcr100.dll, mfc100.dll and other alike.
I don't see dependence of mscoree.dll which is for .NET apps.
It has shw32.dll which is SmartHeap memory management. And the api is just a wrapper. It is true that they used a lot of .Net for macros, plugins and other.
If all the binary and dll files I looked at are encrypted (not obfuscated) and decrypted, JIT ed in ram at runtime it is possible to be fooled by it's protection, I don't think that's true so until someone will provide strong evidence Tekla for me is written in c++. Not that it actually matters.