DocumentFormat.OpenXml.dll Not Working on Windows server 2008 R2 - openxml

In my C# asp.net web application, used DocumentFormat.OpenXml.Dll to work with Excel file generation, it is working in one application server, but failed in another server, what would be the reason for it. How to check it?

Related

Entity Framework: Setting correct connection string to SQL Server Compact in ASP.NET MVC 4

I want to use and embedded SQL Server Compact edition in my asp.net mvc 4 project. I try to approaches but I have problems with any approach:
First attempt
I have created a new data connection from visual studio and from server explorer of type Microsoft SQL Server Compact 3.5 and I store the .sdf file in my asp.net mvc 4 project under \App_Data folder (I add this .sdf file to this folder). I guess doing this I create and embedded SQL Server Compact database for my web application, am I right?
Finally, I create the following connection string in web.config:
<add name="DefaultConnection"
providerName="System.Data.SqlServerCe.3.5"
connectionString="Data Source=|DataDirectory|\App_Data\MyDatabaseSQLCe.sdf" />
I start my web application but an error occurs, database seems to be not found, well the error says something like:
SQL Server Compact is not intended for asp.net development
I am not sure if the connection string above described is the correct.
Second attempt
Also I have downloaded the SQL Server Compact 4.0 from here:
http://www.microsoft.com/en-us/sqlserver/editions/2012-editions/compact.aspx
and I have installed. Once installed If I go to create a data connection as above described it does not appears SQL Server Compact 4.0 from Visual Studio. I would like to use an embedded SQL Server Compact in my project but I am completely lost.
Conclusion: my goal is to use SQL Server Compact edition as embedded in my asp.net mvc 4 web application and put this .sdf file in my \App_Data folder and make it works with the correct string connection in web.config.
|DataDirectory|\App_Data yields App_Data\App_Data, if I am not incorrect. Try Data Source=|DataDirectory|\MyDatabaseSQLCe.sdf.
You can test this by dumping AppDomain.CurrentDomain.GetData("DataDirectory").ToString() on your webpage.
You should grab the toolkit for visual studio when dealing with Sql Server Compact.
http://visualstudiogallery.msdn.microsoft.com/0e313dfd-be80-4afb-b5e9-6e74d369f7a1

Deploy the asp.net MVC 2 web application to the IIS 7.5 getting issues

I have developed the asp.net mvc web application. whereas my macine is configured with IIS 7.5. I want to deploy my web application with source code to the IIS so that i can attache the process and debug it run time. I choose this way because few functionality , like file copy and file create not performing after simple publish.
I tried by ,
Create the web application in IIS 7.5 manager. installed ASP.NET utility. As i browsed , I got asked by to enable directory browsing.
Which i enabled. where as in IE I found file structure which definitely did not want. I expected direct my LogOn page which is configured in globle.asax after deployment.
What else i need to check. or is any step i have missing?
I am using Visul web developer 2010 express edition to develop the application.
Please guide me.

deploy mvc2 application in IIS7 in Windows Server 2008 R2

I am trying to deploy my MVC2 application on the IIS7 of my Windows Server 2008 R2 to allow non-developpers to test it.
I deployed through webdeploy, it didn't work.
I just copied the files after a build, didn't work.
I copied the published file, didn't worked...
When I click on the web site link in my IIS, nothing append.
I don't know what I am doing wrong..
Somebody could help me?
Thanks in advance
If you can give some more details on what happens when you try to browse to the site on the server (do you get a yellow screen exception, 404 error, etc) it will help to identify the cause. Without knowing more details, here are some suggestions:
If you don't have MVC 2 installed on your server (which is not a requirement), make sure you are doing the following:
In your Visual Studio project, under References, make sure you set the "Copy Local" property to "True" for System.Web.Mvc. This will deploy the dll to your site bin dir when you do a web deploy.
Make sure the .NET Framework version 4 is installed on the server. See here for more details.
In IIS, make sure the Application Pool that the site is using is set to use v4.0 of the .NET Framework.

Creating PDF from RPT file in Classic ASP

I have a windows 2008 application server that hosts a web application built in classic asp. i have a crystal report server which is a windows 2008 server. both are on the same network.
I want to create pdf file from rpt file in the application server. Is there a way to do this without installing crystal reports on the application server?
-Vivek
This requires a bit more thinking but in theory you could do something like this:
Classic ASP is not able to work with Crystal Reports (as far as I know)
However, your IIS7 is able to handle both ASP.NET and Classic ASP
You could develop a service in .NET that does the conversion for you
This could work on your application server utilizinig the Crystal redistributable runtime libraries
Like I said this is just a theory. Give it some thought and if you run into any trouble let me know...
I don't know nothing about Crystal Reports Server, but surely there a way to tell the server to process a file and generate a PDF. You can then pick up the file from the other server.
you can use crystal reports from classic asp but you have to use the crystal reports dlls on your application server (where asp is executed)
dim oApp : set oApp = Server.CreateObject("CrystalRuntime.Application.10")
and so on...

ASP.NET Ajax client framework failed to load

We developed an web application using visual studio 2008. In my development PC, the application is working fine. In production server I am getting the following exception "ASP.NET AJAX CLIENT FRAMEWORK FAILED TO LOAD". What should I do to make it work?
Thanks,
P.Gopalakrishnan.
I'd start with making sure all of the appropriate service packs are applied and that the 3.5 framework is actually installed on the box.
Also, make sure any assembly you reference that isn't part of your deployment is gac'd on the machine. Check version numbers.
All else being equal, I'd guess the server is just way out of date on it's updates.