Should we update our product to target VS.NET 2010?

Should we update our product to target VS.NET 2010?

75% - 6 votes Yes
75% 6 votes
0% - 0 votes No
0% 0 votes
25% - 2 votes Give me a chance to update
25% 2 votes
Member Votes: 8, Guest Votes: 0. You don't have permission to vote within this poll.
Whilst you can use both InstantForum.NET & InstantKB.NET  within Visual Studio.NET 2010 due to the fact VS.NET 2010 has only recently been released we still target VS.NET 2008 by default.

We would like to give our users a chance to update to VS.NET 2010 before updating the main downloads to target 2010 out the box.

Would you like us to update the products to target VS.NET 2010?

If you would like to use either InstantForum.NET or InstantKB.NET within VS.NET 2010 please see

I look forward to any feedback :)
Kindest Regards,

Ryan Healey
Blog | Community | Docs

Is there not a way to provide Solutions for each version of VS within the download?  I've seen other developer source products provide this.

For example, you have one ZIP file with two Solutions in the root...  Something like this:



Regardless of the above suggestion, if you choose to only go with one VS solution - provide the one that will allow the largest subset of people to open it with minimal effort (i.e. a simple upgrade).

Al Bsharah: Twitter / Blog

Hi Al

I like the idea of having the solution per version of Visual Studio.  The only problem I can see is this could reduce the speed of availability of fixes / newer versions if the guys have to produce and test various versions of builds.

Personally I would prefer the speed of updates / fixes over multiple versions being made available, and it would take less resource to maintain the downloads area, freeing up more resource for lovely coding! :D

A tough one to call me thinks, I'm sure we all have our own preferences!



Great suggestions Al. This didn't make it for 2010-1 however we'll be looking to provide 2 separate solutions for future versions.

Al How are things with 2010-1?
Kindest Regards,

Ryan Healey
Blog | Community | Docs

Just back from vacation, but am looking forward to giving it a go...will let ya know as soon as it's up.

Al Bsharah: Twitter / Blog

We recently released 2010-3 which now targets Visual Studio.NET 2010 by default.

You can still use VS.NET 2008 for 2010-3 if you create a new ASP.NET project in 2008 and add the InstantASP & InstantForum.NET projects to your VS.NET 2008 solution. Once you've added all projects choose add existing web site and locate your InstantForum2010 web site under IIS. This should bring everything in and allow you to build as normal in 2008.

If you’re a using our developer license you'll need to setup a project reference  to the InstantASP.Common.Data project for the InstantASP.Common project and add a reference to the InstantASP.Common.Configuration project from the InstantASP.Common.Data proect.

I did this earlier today and it took 5 minutes. I'll attach a VS.NET 2008 solution file for both the End User & Developer License once tested further to assist.
Kindest Regards,

Ryan Healey
Blog | Community | Docs

Any idea what I might be missing if I used VS2010 Express vs. a Paid-For version?

Al Bsharah: Twitter / Blog

Hi Al,

Hope your very well. Great question.

To be honest I'm not entirely sure of the main differences. Of course i would expect fewer features within the express edition. I've not used VS 2010 Express yet but will take a look ASAP to get more familiar.

I read the following FAQ but it really didn't answer the key differences…

I know they basically use the same compiler so modifying & rebuilding the DLLS should not be a problem.

I'll dig around and see if i can't find out more Al :)
Kindest Regards,

Ryan Healey
Blog | Community | Docs

With the release of 2010-3 we moved to VS 2010.

If you would like to still use VS.NET 2008 please see...

Hope this helps :)
Kindest Regards,

Ryan Healey
Blog | Community | Docs

BTW, with the dev product I always have to delete the IF2010 web site and re-add it - then re-add the other projects as PROJECTs instead of BINs.

Certainly not the end of the world, but is there any way to get the web site into the solution as a relative path so it can find it when customers open it for the first time?

Al Bsharah: Twitter / Blog
10 Years Ago by Al Bsharah

Existing Account
Email Address:


Social Logins

Select a Forum....

InstantASP Forums