issue: populating values for word document is not happening.object reference error in production server.
development server( working fine)
i am trying to populate the values for the word document using c#.am using microsoft.office.interop.word dll (version 12.0 related to word 2007) as a reference in my project. in my development server office 2007 is installed. am able to populate the values and save the document properly without any error.
Production Environment
getting object reference error. the one difference i see in this server is microsoft word 2010 is installed. i tried my level best but no luck.
*is this because word 2010 is installed in the production server?
*when i hosted the application in the other production server where word 2007 is installed.the application is working fine.
That could be the issue, it looks like Office 2010 uses Version 14 of the dlls:
http://www.microsoft.com/en-us/download/details.aspx?id=3508
Maybe try to use the 14 version in your dev server and see if that works, if so should be ok with production as well. otherwise see if the 2007 dll was copied into you bin, if not try to drop the 2007 version (v 12) into you application's bin and see if that works, could be the production application can't locate the dll in your bin and is then looking in the GAC, GAC would have 2010 version installed. If it's in your bin it might use that one first.
Related
I created a Microsoft Word 2013 Automation process that opens a Microsoft Word template, replaces bookmarks with some texts and saves it as a PDF. It works fine on my local machine because I have Microsoft Word 2013 installed.
However, when this is deployed to the web server it does not work because Microsoft Word 2013 is not installed on it. As far as I know, Microsoft Word 2013 needs to be installed on the server in order for this to work. However, some here believe only select components are needed to be copied to the bin folder in order for it to work and Microsoft Word 2013 does not need to be installed.
Does anyone here know what those minimum components would be? The components I have so far are
Interop.Microsoft.Office.Interop.Word.dll,
office.dll
However it process returns the error message 'Cannot create ActiveX component.' (Since I don't have Visual Studios Installed on the WebServer I don't know which line is causing it).
Or am I correct and we would have to install MS Word 2013 in order for this to work?
In order to automate any Office application that application must be installed and licensed on the machine where the code is executing. No ifs, ands or buts. There is no such thing as "just some components needed".
All that said, running and automating Office applications server-side is not supported and can cause problems (see https://support.microsoft.com/en-us/help/257757/considerations-for-server-side-automation-of-office). For this reason, the Office Open XML file formats were developed, so that Office documents can be generated and manipulated in a server environment.
Is there any hidden tool from MS we can use for BizTalk application migration prior to load solution into VS2015 ? I need some information about what are characteristic we may need to change specially BizTalk.btproj solution to load all project file etc., wonder to know easy approach migrating BizTalk application solution if any.
As various blogs posts and MSDN threads you needed to have an intermediate Development BizTalk environment (BizTalk 2010) and then upgrading it to the later version like BizTalk 2013/R2 and up.
You can download the developer edition here and install the SDK so you can open it in Visual Studio.
The only other way to migrate is to create new BizTalk Projects in Visual Studio 2015 / BizTalk 2016 environment, and then copying the artefacts such as Schemas, maps and re-creating any Orchestrations.
In either case you will have to do extensive retesting as there are certain changes such as the XSLT compiled transform that may cause you issues
No need for a hidden tool. Visual Studio is the tool.
When you open a downlevel Solution, Visual Studio will attempt to update any project and provide a report of what was automatically updated and what could not be updated, requiring manual intervention.
You can do this on a copy of you Solution to get a preview of any work necessary for the real upgrade.
Coming from BizTalk Server 2006, you will need an intermediate version to eventually target BizTalk Server 2016. You can download BizTalk Server 2010 from MSDN. All you need to install is the SDK. You don't need to setup/configure full BizTalk Server.
I am responsible for supporting a relatively complex Website project written with .NET 3.5.
Previously I was using Web Deployment Project with Visual Studio 2010 to deploy this website but at the moment I have only access to Visual Studio 2013.
As far as I know, there is no longer such a tool to be used for deployment in Visual Studio 2013 and I do want to compile the code before deploying to the production server. As mentioned earlier, the project is a bit complex and this would not be easy to be converted to a Web Application.
Any idea?
Unless I missed it, unsure what the issue is - in VS2013, Publish is what you are looking for (either WebSite or Application).
What exactly do you mean by "none of the (vs 2013 publish) options worked"? What is/was the issue?
In one of your comments, you state you want to "pre-compile" (aka "don't want to upload .cs source files) and that's a setting in Publish.
You can Publish to your local file system: "Custom" -> File System:
This extension still exists for Visual Studio 2013: http://www.iis.net/downloads/microsoft/web-deploy
Little bit confused with the question because you are keep referring about website rather web application.
If you are looking to convert web site to web app then you need to follow this: http://msdn.microsoft.com/en-us/library/vstudio/aa983476(v=vs.100).aspx
Otherwise, if you are referring about the deployment project. Yes, it is no longer available.
I'd a very similar situation like you and Since 2013 I have stopped using any deployment project, instead I have started using Publish that creates a deployment package for you on a Network , FTP, Local Drive or even on Azure.
Here is a nice guide from Microsoft
http://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx
If you still want to go for Deployment Project, then you would need to go for "Installshield" limited edition,which is free (http://samirvaidya.blogspot.com.au/2013/11/how-to-enable-installshield-le-for.html).
http://msdn.microsoft.com/en-us/library/2kt85ked(v=vs.110).aspx
I know this is a strange situation, but consider a situation where two programmers are working on one project. One programmer is working on a database driven website in ASP.NET in Visual Studio 2012, while other programmer is working on Visual Studio 2008 on another part of the same database driven ASP.NET website.
What in your opinion is the best way to integrate the two codes?
PS: Downvoters please explain in comments, before downvoting. :-)
Make the second developer update his VS copy to 2012. If you are working with two disparate versions of VS, you will very simply be unable to have either developer work on any part of the codebase that was built with (or upgraded to) the other version.
Once everyone's working on the same platform, and thus can load and build the same solution, project and source code files without error, "integrating" the two codebases becomes rather trivial. Of course, the conversion process may not be so trivial.
My first step would be to ensure that a reliable backup of the entire codebase has been taken; you can copy the flat files to a file store, or more reliably you can use a centralized VCS like Subversion to make sure a single authoritative copy of the codebase as-is exists and can be easily retrieved. Then, while the 2008 dev is updating his machine to 2012, have the 2012 developer pull the whole codebase and load whatever solution the 2008 dev had been working in, and run through the conversion wizard. This wizard will update the XML behind the project and solution files to support features of the new IDE version.
If you absolutely positively cannot get both devs onto the same IDE version, there's still hope. Have the 2012 developer open a new solution file in his copy, and pull in the 2008 projects. If VS asks to convert them, you're SOL; the other dev will HAVE to upgrade, or the 2012 dev will have to revert. But, if the IDE doesn't complain, the 2012 dev can save the new solution under a different name and work with the projects and their source code using that solution file, while the 2008 dev can continue to use the original one. Understand that as long as this state of affairs continues, the 2012 dev cannot use any features of C# 4.0/4.5, such as dynamic types, covariance/contravariance keywords, optional parameters/named arguments, async/await keywords, etc cannot be used in any source code that must remain usable by the 2008 dev. Language-wise, the 2012 developer is limited to C# 3.0, and the .NET Framework 3.5. This does not solve the problem of the 2008 dev not having access to code written from scratch by the 2012 dev in projects created by that IDE; he simply must upgrade to work in these parts of the codebase.
I have installed Microsoft Access Database Engine 2010 Redistributable http://www.microsoft.com/en-us/download/details.aspx?id=13255 on the Windows 2008 server. However, when I ran my web application to import a spreadsheet table to the database. It complains with the error message - "Microsoft.ACE.OLEDB.12.0 is not registered in the local machine."
I have tested my code and works in my Windows 7 local machine. Any idea?
There is a problem with Microsoft.ACE.OLEDB.12 when AccessDatabaseEngine x86 or x64 2010 is installed.
I have long attempted to use the SSMS (2005-2008-2008R2-2012) Export Wizards to export large tables onto Excel and I needed the AccessDatabaseEngine installed to be able to do that.
However, regardless of the MS Office version (2010, x86 or x64, or whatever it is), the 2010 version of AccessDatabaseEngine will not work towards registering the provider.
The solution is to download and install the previous one which is none other than the 2007 x86 one.
This one will work even if Office or SQL Server or VS are x64.
Download it from here http://www.microsoft.com/en-us/download/confirmation.aspx?id=23734
Now, any other propagated issues revolving around the notorious failure to register "the provider" on the local machine for the Microsoft.ACE.OLEDB.12 should be resolved by the above.
Feel free to paste me your experiences on this matter.