How would I know where to find specific documentation? [closed] - c#

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Edit - [Solved]
So recently I have been learning how in integrate MySql Database to Visual C so I tryed finding the documentation to better understand each line of code. I ended up finding its on the MySql website but does not go into much detail.
I then found out through other users questions that some/most of the methods used are actaully inherited from a base interface/class
Example: IDataReader - is the base class
Then programs would inherit from it then make things such as XmlReader and MySqlDataReader
Which can be found here
https://msdn.microsoft.com/en-us/library/system.data.idatareader.aspx
Now here is where my questions starts
How would I have known/figured out where to start looking? If someone did not link me to the exact URL spot how would I have navigated microsofts site to find it in the first place?
What is a ".NET framework" and how would I have known that integrating a database would use it? - It says its Window Based so does that mean different operating system have there own ".Net framework"?
Is it safe to assume if we are trying to combine different applications together they have to have something binding them together hence need of ".Net framework"

MSDN (Microsoft Developer Network) is the umbrella in which all (or at least very most) Microsoft documentation lies. However, this is a huge conglomeration of information, and navigating it is not really an easy thing to give step-by-step instructions for, or even a general overall approach.
What you're facing is a large part "general learning curve", and the other part is a skillset for finding answers, usually starting with google and often ending at StackOverflow or MSDN or various blogs. In time, as the skill grows (and it is very much a skill), you will learn to be skeptical of articles based on various clues, and learn to tell upon reading them whether the author really knew what they were doing (Microsoft's articles themselves aren't without some measure of this variance in quality). Some sites become known as "stay away, they teach bad practices"
"Google-Fu" is an unofficial term that some people use to describe how well they can coerce google into returning relevant information. Often times it's easy, and often times it's quite difficult.
In short, there's no clear answer. Research is a skill to be honed, not unlike programming itself. Start as you are and keep pushing forward, and eventually you'll get a feel for it and get good at it.

Related

Way to gather online data/information and report it to a program? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I asked about this Q format on meta, and the they said that worded correctly, this should be appropriate. This being said, sorry if I still butchered the wording and just in case I'd like to get this across (as was recommended): I'm not looking for opinions on certain things or how they work, rather just the ways it's possible. I don't mean to sound ignorant and I'm truly sorry if I do, it was just suggested to me to say on Meta.
Now for the Q; What just general language at all would be capable of gathering information from public online websites, then putting it in the program where it could be further processed as just any old variable? I'm new to coding and wanted to do this as a little 'introductory' program, to teach myself some new stuff. Problem being, with my idea, I don't even know where to start. Again, I'm not asking for specific ways to do this, I was just curious what languages are capable of doing this at all? I'd prefer to do it in a Visual Studio's language (no preference of which ones), if that's possible.
In short: Are either Visual C#/C++ capable of gathering information online to be further handled within the program? If not, what languages are?
I agree with the comment that this is a complicated first programming task. However, you'll undoubtedly learn something trying it.
If you already had some experience programming in Python, I'd suggest you took a look at http://scrapy.org/doc/ which is a framework (that is, a bunch of classes and other useful tools) which let you write programs to extract information from web pages. Scrapy does let you concentrate on programming by taking care of some of the nasty details involved in parsing web pages.
Another option is to use a javascript framework, maybe something like node.js.
I've done a fair amount of web scraping, and I usually end up using a combination of utilities which clean up web pages and a variety of XSLT processors. I personally find that combination of technology to be easier to deal with; I don't try to use C-family languages until I've basically wrestled the data into shape. But everyone has their own style.
Good luck!

Starting a WPF Business Application From Scratch [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am wondering whether there's a good tutorial that walks you through the development of a full business application that is comparable to the real ones. I have learned the basics of C#, WPF, and programming and web development in general. All the books I have read only shows the syntax and code snippets but very rare shows you the development of a full business application from planning to testing to deployment.
What is the first step when creating a business application using C#/WPF? I know I need to have a plan first. Should I use UML?
What methodologies or techniques should I consider when starting to code. I have read about Domain Driven Design but there is also MVVM patterm. Which one should I use? Should I learn both of them.
I am currently searching for a work in .NET but I really need to know how the developer's workflow in a real life software development team. I have found some books that walks you through the creation of a full software such as Wrox's Problem-Design-Solution books. Does the content of this book comparable to the workflows of a real-life software development?
Thanks a lot in advance and I hope I can find an answer as I am planning to practice my skills to be ready in a corporate environment.
Um, the platform is irrelevant at this point. If you were doing a winform or a web app, would you use UML? If so, then you would also use it in a WPF. If not, fuggedaboutit.
The first step is to careful gather business requirements.
The methodologies or techniques you should consider when starting to code will be handed down to you by the lead of the project. You sound very inexperienced, so the decision will not be up to you, most likely. Every business is different. Heck, every project is different. You may use a different methodology on each of your first 5 projects. Brush up on them, read what you can, but you will always have a learning curve to climb.
You don't need to learn every methodology or paradigm. Learn as you go. Understand the basic premises of a few, especially the standard waterfall, but don't deep dive until you get assigned to a project. Most places I have been don't follow their own methodologies anyway. It's one of those "The Sabbath was made for man, not man for the Sabbath" type things. Organizations will deviate for a slew of reasons.
This is the book I had in college. It has served me well. You car order it for $0.33. Ain't that something. http://www.amazon.com/Software-Engineering-7th-Ian-Sommerville/dp/0321210263/ref=sr_1_25?s=books&ie=UTF8&qid=1342506249&sr=1-25&keywords=software+engineering
Good luck in the field. Just dive in, and work hard. You should be fine.

C# vs Adobe Air for desktop application [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Okay, sorry if I'm a bit vague or little specific. First of all, I'm really new to the business of programming and that kind of things, so excuse my non-knowledge of much of this. :)
Anyways; I've been reading a lot around on the internet on what technology to use and so forth when it comes to application development on the desktop (mainly Windows, since it's my preferred OS). And most of the answers I found said that C# was the way to go and it was the preferred language of choice for Windows (alongside with .NET of course).
Then, I read something about Adobe Air (don't remember where) but at least it interested me. And I then looked around for info about it but sadly there weren't much. But what I found was at least mainly optimistic (and then you have the I HATE FLASH-fan club).
But; since I'm new to this I started wondering about what technology was best and all that, but I just can't make up my mind. But I do understand that for applications that rely on high performance C# is better then Adobe Air.
But since I'm no power user and just want to create simple applications (like to-do lists, sudoku solvers and similar stuff) I'm not sure which one would be preferred or "the best". As far as I've seen Adobe Air have a lot of the good lookin' stuff while C# is the suited-up business stuff.
So, well, basically my question is what language/platform would you prefer for a complete beginner when it comes to simple, not really heavy performance applications? Any kind of answer would be nice. And sorry if the question is bad or something alike, I'm new to Stack Overflow as well. :)
There is no best way - use whatever interests you the most. Keeping up your motivation to learn is the most important thing at this stage.
One thing you might want to be aware of though is that there is a much larger C# community and it will be easier for your to find examples online and get help for C# here than it will be for Adobe Air.
You can create simple to-do list app using both technologies. That can be a great experience for you and give you a closer look at both technologies.
I would say go for C# since you are starting from ground zero. If you already had a bunch of web programming experience then I would say go for Air, but with C# and .Net there are lots of cool things you can do with what you learn.
I would tay start out with a simple "Hello World" WPF application. Once you do that, add a button that changes the text to "weeeeeeeeeeee!" Then add in a slider that changes the text size. Play around. Pick one small step at a time that grabs your attention, and don't give up until it works exactly how you envisioned it. Soon you will be on your way to developing your To-Do app.
Once you get the basics down, the programming world really opens up to you. You can use your C# skills to make a game in XNA. You can buy some inexpensive servo controllers and make physical stuff move around with your programming. You can port your To-Do app over to Windows Phone 7 without having to recode anything. The programming world will be your sandbox. Have fun!

How can I improve my first OSS project [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am still visiting school and will finish my exams next year. Since two years I am working as (the only :-( ) in-house dev for a company providing financial services to Laboratories and doctors. After spending the first year fixing their existing Application and realizing, communicating and agreeing that it won't meet future requirements i rewrote it from scratch. This is my first LOB application.
I needed a "IEnumerable.ToDataTable()" method to do simplify certain things in the Application. I realized that existing solutions wouldn't meet my performance and flexibility requirements, so i came up with a solution based on Dynamically injected IL code myself.
I thought that this might be a good way to contribute to the community, thats why i asked my employer if i may take some of those code and release it under LGPL. They agreed and that's where my first project is:
ModelShredder
Since this is my first OSS project and i am relatively unexperienced with running an OSS project on my own I am asking you for some "best-pratices" and what i can improve on it.
First read this book:
You can download it free of charge here: http://producingoss.com/ There are also some nice screencasts there that may be some use too.
It covers everything you need to know about looking for, contributing to, starting and maintaining an open source project,
It all depends on if you're going to have a team help you or not. It'll be simpler to start doing it yourself if you have the time if for no other reason than you can work out how you want to proceed without worrying about politics.
For a start, any code used as a framework or a library typically needs to be developed to a much higher standard than what you might write for an internal application. This means you need:
Sufficient user and developer docuemtnation;
Unit tests with decent coverage;
A license;
Tagged versions in source control; and
Released binaries and source code with checksums.
Additionally you'll need a method of:
Communicating your project status (release notes, goals, etc); and
A means to allow people to raise and track issues.
Google Code (as just one example) can do pretty much all of this for you.
I would also suggest you register the domain name for your project (typically projectname.org for open source). If the one you want is taken already, you may want to change the project name, particularly as there might be cause for confusion.
The google code pages look pretty good to me. You might want to think about adding a support group on Google Groups.

What should I do to keep a tiny Open Source project active and sustainable? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
A couple of months ago I've coded a tiny tool that we needed at work for a specific task, and I've decided to share it on CodePlex. It's written in C# and honestly it's not big deal but since it's the first project I've ever built from scratch in that language and with the goal of opening it from the very beginning, one ends getting sort of emotionally attached to it, I mean you'd wish that the people will actually participate, be it criticism, bug reporting, or what have you.
So my question is, what can I do to actually encourage participation, stimulate curiosity or just recieve more feedback about it?
By the way this is the project I'm talking about: http://www.codeplex.com/winxmlcook/
You should:
Promote it where you think it would be relevant (forums,mailing lists etc.). Try not to spam though - it will create a backlash.
continue to provide updates as to create the appearance of an active project until more people pick it up.
Find project leaders, they are the sort of contributors that encourage others to contribute as well.
Blog about it and link to relevant blogs (creating ping-backs). Also leave comments at relevant blog posts.
Basically, your generic Internet marketing tactics ;)
You first have to acquire users by marketing the tool. Once you have users, that naturally means you'll start getting feedback.
One thing I noticed is your project description doesn't sell the project well. For example, type "winxmlcook" into Google, what gets shown is your project description but it's not likely to get someone to click on it.
I know I sound like a broken record constantly posting this book, but just about everything you could ever need to know about running an open source project is here. In particular, pay attention to these two chapters:
Getting Started
Managing Volunteers

Categories

Resources