Couple of customers are still using Visual Interdev and VS.net 2003.
Now the only way i know to get those editors is by having a msdn premium subscription.
Wanted to check can a MSDN professional subscription also get me older VS softwares?
-Paritosh
Check out the MSDN Subscriber Downloads and MSDN Subscriptions Index pages.
VS2005: Yes
VS2003: No
InterDev: No
Related
http://cmsreport.com/content/2010/03/ten-content-migration-tools-sharepoint-platform is a link that shows many software that exist migrating "content" from a 2007 to 2010 platform.
Barring web farm / sql server 32 - 64 bit issues, what is that which will NOT be migrated (assuming that I do a Attach / detach database upgrade method. In place upgrade is not an option in my farm.
I have a web farm with one app server and one sql server box.
Thanks in advance
Note: I did look at other similar posts but they did not have the kind of information that I was looking for.
Have a look at the following Technet article which should give you a starting point for planning your upgrade:
http://technet.microsoft.com/en-us/library/cc303429.aspx
The article should give you an idea of what to plan ahead for and what the pros and cons for each method would be.
I am trying to create link SQL Server 2005 Report Server Reports in VS 2010 and I get an error "Remote Report Processing requires Microsoft SQL Server 2008 Reporting Services or later". How do i downgrade the control to the one from 2008?
Unfortunately, the only way I know how to get around this is to use an older version of Visual Studio for this type of development. Not much of a solution though.
You will have to use the 2005 version of the report viewer control. Unfortunately MS doesn't allow this to be used in 2010. There's probably a better technology-related reason than "Make you upgrade to 2008", but that's how I feel about this.
However, You have some hoops to jump through:
The old control must be put on a WinForms form with VS 2008 (or 2005).
The new application must be using the full .Net 4.0 profile.
If your main application is signed, the DLL you create in VS 2008 must have a strong name key.
The form in VS 2010, containing the control you built in VS 2008, will not open in design view in VS 2010.
If you're using WPF, there is no native control - you must resort to Windows Forms Interop to make this happen, hosting the WinForms control.
Also keep in mind that there are several versions of the Report Viewer control out there:
- v8.0 = VS 2005, VS 2008, SQL 2005
- v9.0 = VS 2008, SQL 2008
- v9.X = VS 2008, VS 2010, SQL 2008 R2
- v10 = VS 2010, SQL 2008 R2
Hope this helps you.
I believe I have found a bug in Sharepoint 2010, and would like to submit this to the product development team.
I tried to use Microsoft Connect, but it seems that Sharepoint 2010 is not in the active list of products that are receiving Feedback.
Does this mean that the bug reporting stage for MOSS (Microsoft Office Sharepoint Server) 2010 is over? And it is no longer possible to submit product bugs?
Is there another channel of general public communication with the product team? I have an MSDN subscription if this helps.
No, it doesnt in directory.
http://connect.microsoft.com/directory/business-software/
There is an entry for Sharepoint Community under Business Software. And they are accepting bugs as well.
We are trying to configure SharePoint 2010. We realized that SQL Server license for SharePoint is very costly. We are now evaluating other options for SQL server. We would like to know whether we can use MySQL with SharePoint 2010. I appreciate your response.
Not as the back end for Content databases. Only SQL server is supported.
Why not install SQL Server Express R2? That is free.
See: http://sergeluca.wordpress.com/2010/06/30/with-sharepoint-foundation-2010-use-sql-server-2008-express-r2/
(So that's an option if you're not storing many documents.)
Alternatively, look at processor licensing, as that is much cheaper then per user licensing. (Generally).
I doubt you need SQL Server Enterprise edition, so look at the Standard edition licence costs.
We've found that Windows Server 2008 SP2 doesn't contain QEDIT.DLL.
This 'DirectShow Editing' DLL contained several useful DirectShow filters, namely SampleGrabber, that we had been using.
I found some references to this issue during the Windows Server 2008 beta cycle, but it was supposed to have been added back for release.
Does anyone have any current knowledge of this, and if there are any workarounds other than copying a version from Vista or Win2003?
The SampleGrabber filter is one of the MSDN sample filters. I'm not sure whether all the filters that you need are available as samples though.