i just started developing mvc apps with monodevelop, and when i try to deploy to my hosting server, which is Windows 2008 R2 with IIS 7, i can not get it to work, because some of the referenced libraries (Mono.Data.Sqlite, etc) are not published.
Does anyone had the same problem? How can i publish the mono libraries with the project?
No, you don't have to install mono . Just be sure that the libraries are included or project deploy (or copy them to project) or copy them to server's GAC.
Your server will need to have mono installed too.
Related
I've currently used the System.Data.SQLite DLL in a .NET 4.0 x86 WinForms app. This is causing an issue on one of my client's PCs although I cannot reproduce this bug on my system. Both systems are 32bit Windows 7. How do I solve this? Things I've tried:
Installing .NET 4.0 (the app is .NET 4)
Installing all possible VC++ Runtime versions from 2005 to 2012
Installing this particular VC++ Runtime that SQLite needs (fixed a similar issue on my PC)
Adding the useLegacyRuntime attribute in the app.config XML
The error looks wierd because my app is obfuscated. The app works on my 32-bit PC and on my 64-bit development PC. It fails on a client machine. What can I do to solve this error?
In your project, solution explorer expands the Reference section and right click System.Data.SQLite then open properties, in the properties window, make sure copy local is set true . After that rebuild your project and run your client machine again
Turns out my SQLite DLL was outdated. I downloaded the latest from here and rebuilt my app with it. It worked on my PC as well as the client's. I had to install VC++ Runtime 2005 x32 on the Client Machine as well.
Disclaimer: I am a total noob when it comes to anything .Net, but I have to get stuck in for a project I'm working on.
I see there are already some posts on this here, but no complete answer on how to resolve this. I get this warning:
Can't find PInvoke DLL 'sqlceme35.dll'
when trying to deploy to a Windows Mobile 6.5.3 emulator from Visual Studio (I'm coding in C#). I am obviously using Sql Server CE for the application. I see it deploys just fine to emulators running older versions of Windows Mobile (namely 5.0).
Could anybody please explain this?
sqlceme35.dll is not part of a standard Windows Mobile SDK installation and needs to be installed separately (see https://www.microsoft.com/en-us/download/details.aspx?id=8831) and deployed manually (copy and install CAB file from your PC after install, see https://msdn.microsoft.com/en-us/library/13kw2t64%28v=vs.90%29.aspx).
In your case you need to install the cab files from the wce500 subdirectory. ( "drive:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Devices\wce400 or wce500\CPU architecture type").
Although the site https://technet.microsoft.com/en-us/library/ms172361%28v=sql.105%29.aspx states that SQL Server CE runtimes will be deployed automatically, this is not always the case. So best is to manually install the runtimes before running an app that depends on them.
C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.5\Devices\wce500\armv4i
Get the following cab files:
sqlce.wce5.armv4i.CAB
sqlce.repl.ppc.wce5.armv4i.CAB
sqlce.ppc.wce5.armv4i.CAB
sqlce.dev.ENU.wce5.armv4i.CAB
Install those onto the Program files directory of your pocket pc. Once they are installed, you will then see a folder called "Microsoft SQL Server Compact Edition". It will have the dlls that your application uses.
i finally finished a proyect i was requested in my university with Lightswitch. Im ready to deploy (publish) next week, and i was JUST told that the people that will recieve the software, are using XP machines. I've read a lot of questions and lots of fixes, to get Lightswitch working on Windows XP, like:
Changing the DumpBin with "editbin vslshost.exe /SUBSYSTEM:WINDOWS,5.01 /OSVERSION:5.1"
deploy it as a desktop application with the services deployed to IIS (i dont think this will work because those are really old pc's)
install all the prerequisites manually and launch the ClickOnce application directly from deployment manifest file (.application)
create a sample ClickOnce application using Visual Studio 2010 OR Visual Studio 2008 with the same name as mentioned in Visual Studio 2012 and publish it. From the published location take the setup.exe bootstrapper and replace the existing setup.exe bootstrapper created using Visual Studio 2012
With all of this workarounds available, i NEED to ask, will this ultimately work? Can someone REALLY tell me that using one-or-all of this workarounds i WILL be able to deploy the application!?
Someone?
The 2-Tier Deployment issue on XP was also addressed in VS 2012 Update 2 IF you upgrade to a "V3" LightSwitch project by right-clicking on the root project in Solution Explorer and selecting "Upgrade Project". This updates the project to the "V3" project system, runtime and will use a much newer publish wizard. The version of VSLSHOST.exe that ships with VS 2012 Update 2 is compatible with XP.
Dave Kidder - LightSwitch team
http://social.msdn.microsoft.com/profile/dave%20kidder/
I have a successfully deployed application using the 3-tiers running as an out-of-browser (desktop app) on XP. Initially I was going to do the 2-tier deployment, but I was unable to get a workaround to work.
So I have one server, which runs IIS as well as my SQL server (OS is Windows Server 2003, but doesn't have to be.)
The client machines range from Windows XP to Windows 7, and I haven't had any special problems with windows XP.
So I can definitely say XP will work as a client. I was unable to get it to run the middle tier (hence IIS on the server) but I didn't try every last idea I found, so I won't say it's impossible.
The two links I found most helpful in the process were
http://blogs.msdn.com/b/bethmassi/archive/2011/03/23/deployment-guide-how-to-configure-a-web-server-to-host-lightswitch-applications.aspx
and
http://blogs.msdn.com/b/bethmassi/archive/2012/03/29/lightswitch-iis-deployment-enhancements-in-visual-studio-11.aspx
Hope that helps.
I need to check these things before i procedure with an installation:
Does target machine(tm) has installed .NET 3.5?
Does tm has installed IIS 6 (win xp) or IIS7 (win 7)?
To check which OP is installed the tm... If it is XP, i need to check does it have service pack 3 and is in both cases (xp or win7), is it 32bit or 64bit op?
Thanks in advance.
Use ClickOnce to Deploy your application
Goto Project Properties
Click on the Publish Tab
Add the PreRequisites like .Net 3.5,Sql Server etc
Publish Now
Else if you are using Setup Deployment Project, you need to write some script to know all these information.
If you are using ClickOnce you can develop small class to know the Service Pack etc
SqlServerCe doesn't seem be supported in .net 4.0. But since I needed an embedded database in my application, I gathered all the necessary 3.5 dlls and included them so that my wpf application could use SqlServerCe as its embedded database.
The application works on my development machine, but now that I've created an installer, and am installing the application on other machines, I keep getting this exception on hose machines:
Unable to load DLL 'sqlceme35.dll': This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)
That dll is definitely included in directory where the application is installed. I've even tried copying all related SqlServerCE dlls to the System 32 folder. Nothing I've tried so far has resolved the problem.
Any suggestions?
I just recompiled an app I have that uses SQL Server CE 3.5.1 in .NET 4.0 and it works just fine. Here are a few things to check:
Are you including all of the SQL
Server CE DLLs in your installer?
There are 7, not just 1. The others are native DLLs which are the actual core of SQL Server CE.
SQL
Server CE has x86 and x64 version
DLLs. Are you using the correct
version for the OS you are
installing on?
I resolved my problem by installing:
Microsoft SQL Server Compact 3.5 Service Pack 2 Beta 2 for Windows Desktop:
I solved the problem by installing the Microsoft Visual C++ 2008 Redistributable Package (x86)
In my case the Microsoft.VC90.CRT.manifest from \bin\amd64\Microsoft.VC90.CRT respectively \bin\x86\Microsoft.VC90.CRT was missing. When deploying your solution, it isn't part of the release by default but on some servers it seems to be necessary.