I need to provide an editor as a part of my application.
The MS Word lends itself as a most convenient one but the GUI customization API in versions above 2003 is not flexible enough for my needs. So it has to be Word 2003. All my users have MS Office
installed but many of them have version 2007 and 2010. I want to setup MS Word 2003 as a part of my
application. Office 2007 or 2010 and 2003 function well side by side so no problem here.
But the question is: Is it legal? Can I add the MS Word 2003 setup MSI to my installation package?
You won't be able to legally distribute MS Word 2003. Are you writing a Windows Forms application? If so, why not use the RichTextBox widget as part of your app?
It's not legal, if you readed the License whe you install it, you should know that redistribuitable (i think it's mispelled) is not an option.
Sorry, you should find another way
To the best of my knowledge, the answer is No. This isn't legal. A possible recourse is to use COM+ or DCOM.
Related
I've happily created an MSSQL database which, from my point of view, works well and gives me what I want. If the boss wants info from it, he could ask me. It would be better if it had a front end.
I've looked around and seen recommendations for Visual Studio/Lightswitch and ironically am a little in the dark....
1) Presumably VS 2013 and Lightswitch aren't the same thing, or is the latter part of the former?
2) I've easily connected my SQL to a trial version of VS 2013, but cannot make what I would call 'forms' in any other app (such as Access) which can call and update data.
3) Before I venture on and spend further time in this avenue, does anybody know if VS2013 would be able to build the app I need on a desktop to access SQL?
Thanks in advance
What are some good database solutions that support Silverlight and are solid for a small-medium traffic website
Easy to use/Manage is a very strong plus
edit: Forgot to mention that the database needs to be very smartphone-friendly, it needs to be able to work with devices on iOS, Android, and Windows Phone 7
It depends on what you term small-medium. I would say SQL Server Express should suit your needs.
It is free, but your database size cannot be more than 10 GB. It also limits the resources that can be used from the server.
http://www.microsoft.com/express/Database/Default.aspx
Silverlight is not bound to a database.
Every database available to ADO.NET is usable within .NET.
MSSQL Express is a good solution (especially in .NET env) as well as any other like MySQL.
SQL Server Express is a pretty obvious choice. Integrates very well, tons of first class documentation, very reliable, good management studio, upgradeable to more powerful versions etc.
Considering your edit, it appears to be a windows phone 7 app that you're going to make, and that you want the database stored on the phone (as opposed to connecting to an internet based datasource). In that case, you might want to take a look at SQL Server 2008 Compact.
Scott Hanselman has an article about using EF Code First with SQL Server Compact (His solution does not specifically include Silverlight, but it works just the same iirc) here.
I need to know wether or not to buy the VS 2010 premium or not. I have the Visual StudioTeam System 2008 Database Edition working on my own version of vs 2008 team suite. My coworkers only have VS2008 professional. We are moving to VS2010 now. We do not have MSDN licenses for our company right now. We are looking to buy just the VS2010 no MSDN. It is very pricey to get 6 licences of VS2010 premium. We need to get our database into source control. We are currently email scripts around, and it very difficult to keep track off. Are there any non-microsoft solutions that would be the same features and be free?
Does the entire team need the Premium functionality? Contrary to the title of your question, VS2010 Professional does include the Database Project. What you don't get is schema compare, data compare, data generator, unit testing, refactoring, and static code analysis. So one compromise option would be to get one Premium for the person who needs the above tools, and leave everyone else with Professional?
How much time do you lose on your projects emailing data model changes around? How much extra time does the team spend debugging because of using that process? If you add up all that time, look at what could have been built instead and general developer happiness; maybe the price for VS Premium isn't so bad.
I'm just saying its easy to be blown away by sticker shock on tools until you add up all the lost time that could have been going to money making product development.
For database projects you definitely need what they call a "data dude" (Database Edition) or Team System (for 2008).
For 2010 it's either Premium or Ultimate.
Another option would be to move database development into the main (non-database project) by using some ORM tool. Either Linq2Sql, Entity Framework or a third party solution like nHibernate.
When looking for which version of Delphi 2010 to buy, we found the following limitation on the professional one:
Delphi 2010 Professional is designed
for developers building
high-performance desktop GUI and
touch-screen applications with (or
without) embedded and local database
persistence.
What does this really mean? Does this mean that we'll only face this restriction if we choose to use the native vcl components for database access we'll face this restriction.
And what if we choose to use ADO components instead of those? In this case, how can Delphi avoid us to access remote database servers? Did anyone here ever tried this?
Going even further: if we choose to use a database like Firebird, which is just one file, and used a network mapped drive. Could we be facing the same limitation?
Supposing we opt for ADO, what will be the main consequences?
As I understand it, they're referring specifically about dbExpress and doesn't restrict you from using dbGo or some third party library to access remote databases.
Does this mean that we'll only face
this restriction if we choose to use
the native vcl components for database
access we'll face this restriction.
Yes. The professional version simply leaves out some of the driver & driver technology that natively supports certain databases. It still includes ADO support and there are plenty of third-party drivers that you can use to access other databases.
Delphi 2010 does not include any technology to stop you from building applications that interact with remote databases aside from the fact that it does not include DB Express (its own database driver technology).
DataSnap is not included in the Pro version either. I got quite interested at a recent Delphi workshop when they showed off DataSnap only to discover when I got back that it's missing from the Pro version.
So I'm back to sticking with my SDAC components and other third party middleware components. Works perfectly without the expense of the enterprise version.
The SQL Server dbExpress driver isn't included (amongst others) but the ADO/dbGo stuff seems to work just fine over the network. But we haven't used the Delphi supplied DB drivers since Delphi 3 due to them keep changing their mind about the latest silver bullet for DB access (much like MS do/did).
Could the SQL Server IDE ever become an application development platform for enterprise applications? In a similar way to the old xBase applications, but, you know, better?
The main reason is that the Management Studio is one of the best “data centric” application I’ve ever used. It has most of the main ingredients for the proposed solutions:
powerful data manipulation language (SQL :o) )
good security
distributed architecture
The main features that it lacks:
a GUI toolkit: something simple and standard, enterprise applications usually don’t require fancy UIs
some form of automation (.Net, COM, I really don’t care as long as it works)
MS Office integration (especially Excel)
So…?
UPDATE:
The question above is a request for feedback on an idea. I'm not planning to use SSMS to build an interactive application in the near future. I would really like to hear what do you think about it and what other suggestions you might have (maybe there is already a product which does exactly that).
A shorter text for the question would be "If SSMS and MS Access could marry, how would their child look like?"
2nd UPDATE:
"Microsoft announces its new product codename 'Frankenstein'. The new product tries to combine the ease of development of database applications from the old Fox Pro and Access times, with the brand new SQL Server 2012 suite. As 'Frankenstein's Product Manager, Jim Bob, stated "[Frankenstein] will enable the developers to shut the f*#k up, and just build that thing already. Not spend their (highly remunerated) time arguing what's the best ORM, or AJAX toolkit, or should they use SOA etc... (btw, since 2009, SOA is dead)"
Well it depends on what way you look at it.
You can extend and build plugins for management studio but you can also use the visual studio shell as the base for new applications (altho I don't think this is what you want?)
However re-reading your question it looks like you actually want to build applications for SQL server. In that case you might want to check out Visual Studio Team Systems Database Edition
There's two risks involved with building applications on top of SQL Server Management Studio.
First, SQL Server Management Studio has been fairly consistent from 2005 to 2008, but that's only three years of release time. SQL Server 2000's tools were dramatically different, and there's no reason to expect SQL Server management tools to always remain the same.
For example, at the Professional Association for SQL Server (PASS) Summit in Seattle in 2008, Microsoft demoed a new management framework for SQL Server. The databases will be packaged and managed in a way quite different from what we're used to in SSMS. Project Kilimanjaro (think of it as SQL 2008 R2) will be the "down payment" on that management, with the rest of the tools coming in later versions. SSMS will look, feel and work differently in order to accomodate this new way of building database-driven applications.
Second, Microsoft's architecture for SSMS is not pluggable, and they haven't encouraged any third party development inside SSMS that I'm aware of. You can build some level of interactivity by using RDLC reports - standalone SQL Server Reporting Services applications that run inside SSMS - but for the most part, you're not encouraged to build atop SSMS because they do want the right to change it when they need to improve it.
I've got good news, though - you mentioned that you'd want some kind of Office tie-in. Keep your eye out for Project Gemini announcements. Donald Farmer did demos of it at PASS, and there's probably some video circulating around. It uses Excel as a front end for BI analytics, and they used million-row-spreadsheets that were storing data back in SQL. There's not much out out yet for the public, but keep your eyes peeled.
To answer the shorter question - Have you seen the various Frankenstein films?
The longer question - why would you want it to, you already have Visual Studio? SSMS is an excellent environment for developing stored procedures, queries, views and the like, lets leave it that way. And anyhow, the only good XBase environment was FoxPro and look where that ended up.