Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Hey there,

I have a complete project that isn't functioning properly in IE.

I was wondering what SO's policies are on posting the entire project and letting people pick it apart?


share|improve this question

migrated from Jul 30 '10 at 10:43

This question came from our site for professional and enthusiast programmers.

Why not just post the particular areas that are not working in IE? – Liam Spencer Jul 30 '10 at 10:41
Probably a better question for But the response you'd probably get is: post the smallest set of code that demonstrates the problem. – Tim Robinson Jul 30 '10 at 10:42
Yep. This isn't a "fix my project" site, and such questions (in my experience) tend to be downvoted quite quickly. Well done for asking though... – spender Jul 30 '10 at 10:43
That's cool, thank you for your answers - I was just curious :) – Barrie Reader Jul 30 '10 at 10:54
Possibly a duplicate of mine?… – detly Jul 30 '10 at 14:08

I think there's nothing speaking against linking to the entire project on an external location (like a github repository, or even a ZIP file).

Chances are, though, that nobody is actually going to pick through your project. "Fix my code" questions are generally not very well received on SO. The expectation is that you work through your project and identify the problems - I'mn sure the SO community will be happy to help you with those.

share|improve this answer
As long as you don't say "can somebody make this work", you're probably ok. Most good questions, IMO, are the kind where someone has some code that doesn't work, they explain what they've done so far, post their non-working code, and ask for help in understanding why it doesn't work. Usually, this ends up with an answer with working code or, at least, a pointer to the right direction to take to fix it. – tvanfosson Jul 30 '10 at 10:49
I've never looked at the few zip-files posted at SO - i'd have to download them first, decompress, open in some viewer, ... Online viewable sources have a much higher chance of people looking at them. – Georg Fritzsche Jul 30 '10 at 13:34
My experience is that "fix my code" questions attract answers (at least in C and C++) provided the OP posts a reasonable amount of code (enough to show all necessary context, not enough to be overwhelming), has at least one specific problem, and shows signs of having worked on the program. – David Thornley Jul 30 '10 at 13:45

Regardless of StackOverflow's policies, people aren't going to take very well to you posting a ton of code in a question. In addition, asking someone to fix your whole project seems too much like asking me to do your work for you. Narrow down the problem to the smallest bit of code that seems to be causing the problem(s). This is good debugging practice anyway. If in the process you solve the problem, great. If not, post a question about that tiny bit. Likely, you'll get an answer that helps and then you move on to the next bit.

share|improve this answer

I think the policy is: don't

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .