I made an application that I put onto the hard disk of Win CE (the Compact Flash card). My problem is that the application is using the SQL Server CE 3.5 database but it looks like that the image is created with the SQL Server CE 3.0. I couldn't select the 3.5 version when I started to build the image.
The 3.5 version dlls are deployed every time I debug the application so the problem never shows up in the development phase.
Now when the application starts (it is started automatically when OS boots) the message window with exceptions pops up and don't let the application to start. My question is how to install the SQL Server CE 3.5 into the image or how to install it using CAB files later or on every boot up time.
When I run the correct CAB files (three CAB) on running OS system it installs the 3.5 version and my application starts but when I reboot the OS again the changes are not saved and commit. There must be a solution to add the 3.5 version in the catalog before building the image or to install it on every boot up time or the last option to install it permanently once after the first boot.
If you can provide me the solution to install the CABs every time the system boots up It will work for me but then take into the consideration that I have to run the application that will use the SQL Server CE 3.5 database on system start so the installation of the CABs must precede the application autostart.
Thanks in advance.
You have a few options. The least desirable is to run the CAB at startup.
One option is to put the newest SQLCE binaries into the OS if you can. This is available in the catalog, provided you have all of the updated QFEs installed. If, for whatever reason, you can't install the QFEs, you could always replace the source binaries Platfrom Builder pulls from at %WINCEROOT%\OTHERS\SQLCOMPACT.
Another option is to just include all of the SQLCE binaries in your application deployment. You don't need a CAB, just put the DLLs in your app folder (removing SQLCE from the OS is a good idea if you go this route to prevent native DLL collision). The source for these binaries is at %PROGRAM_FILES%\Microsoft SQL Server Compact Edition\v3.5\Devices. This is actually the route I prefer, as an update to SQLCE doesn't require a new OS.
Related
I have built an Application using visual studio 2010 and a setup using the Visual Studio installer. Now what I want is whenever the exe is installed on a client machine it should check for updates regularly.
Any Suggestions . Please Help.
It's my experience that most people do this in the app itself, so that when it runs it checks your web site for updates.
Basically you need a web service call to which your app passes the ProductCode and Version of your setup, your MSI file build. At your web host you need a database (or Xml file) that has information on the latest available version and it's download location so that you can return that information to your app, assuming the latest version is higher than the running one.
You're in Visual Studio, so you build a RemovePreviousVersions updated MSI, and that's what you download and install. If the install needs admin rights and your app isn't elevated than you'd launch an external exe with an elevation manifest to get it installed.
I just finished a project similar to this, but instead of using Visual Studio installer libraries, I created a windows service that runs on a 10 minute loop, and when the service detects a new version, it kills the running application and performs a download and copies the new files into the application folder.
There are a few things you need to take into consideration; 1) A way to gracefully warn and then close the application so the user is not angry over a forced kill of the application. 2) A web location to store the upgraded application files, and a web service to advertise the available application versions. 3) A way to queue the upgrades so that when a new version is released not every client will be upgraded at once (flooding your web server with upgrade requests and downloads).
This technique is used by Adobe for upgrading and installing applications such as Acrobat Reader and Flash.
I have a windows server 2012 data center server where I configured a web application. I can't tell whether it is a core version or not as I want to install other application which are not compatible with core versions.
The server is fully GUI enables but from google I found that core versions doesn't have GUI. And according to the following link, I went to the regedit and found out that it is a core version but my server is fully GUI and all applications like explorer are there.
https://msdn.microsoft.com/en-us/library/hh846315(v=vs.85).aspx
Is there a way a core version may have a GUI or I am missing something? How do I tell if is a core version?
Thanks
D.
As you can see in this link : https://msdn.microsoft.com/en-us/library/dd184075.aspx?f=255&MSPPError=-2147217396
The core version "GUI" is only a command line interface.
There are a few GUI programs you can run, the complete table is provided on the link above.
You won't be able to open any window explorer whatsoever on a core version.
Another way to test if Server Core is running is to check the registry under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion for the value of InstallationType. If it is set to "Server Core", then the Server Core installation option is installed.
I supposed this is what you tried to do.
To make it simple, if you have a start menu bar and other windows than the command line interface as you log in to your server, this is no server core =)
I'm currently working on a project which has a Winforms component that is installed via ClickOnce. The original target OS was Vista and above and it continues to work fine for those platforms.
However, the customer has now requested that the application be tested against Windows XP (yes - I know it's about to have support dropped but what can I say).
When I run the installer against a fresh XP virtual machine ClickOnce duly installs the prequisites (Windows Installer 4.5 and SQL Server 2008 [with configured instance]) before installing the application itself.
Running the application appears to work as expected but when attempting to sync the local database with the remote one an exception is thrown.
"Could not load file or assembly 'Microsoft.SqlServer.Replication,
Version 10.0.0.0' or one of its dependencies"
Now, if I start again from a clean XP VM and Manually install Windows Installer and SQL Server Express 2008 before starting the ClickOnce package to install the main application the resulting installation works fine and without error!
I have tried numerous things including creating a ConfigurationFile.ini and using that for both manual and ClickOnce installations but the result is the same - the one with the manually installation of SQL Server will run without error but the ClickOnce installation will not.
I've pretty much run out of ideas now so hoping that someone can point me in the right direction.
Thanks in advance
Version 1.5 of my Windows Phone app uses Version 1 of a 3rd party Isolated Storage library. I Version 2 of this library has performance improvements and bug fixes. I would like to upgrade my app (make it Version 1.6) to the new version but would like to test that data is not lost during upgrade.
I deployed version 1.5 to the phone and when I deploy version 1.6 from VS2010, the previous app and data are lost. My app is not upgraded but simply replaced.
How to I test the upgrade?
Thanks
You should deploy from within Visual Studio after rebuilding the xap, not using the xapdeploy tool - see this article for an example:http://gusperez.com/wp/2010/12/22/update-testing-your-windows-phone-7-apps/
I'm guessing that you have 2 separate project which each have the same ProductID (in WMAppManifest.xml). This would explain why the first app is being uninstalled when the second app is deployed.
I'd test this by manually setting the contents of Isolated on the first run of the new version of the app.
There are 2 approaches you can take:
- Manually set the contents of the files in IS (either in code or during debug)
- Use a tool like Isolated Storage Explorer
I would probably do something like:
You can use Isolated Storage Explorer Tool (ISETool) to copy the isolated storage files from your old version into a directory (which you would commit to source control).
Create a Build Configuration called "Debug - Upgrade from 1.5"
Define a Post-Build Event that copies the data from the 1.5 backup directory to the emulator (it will need to be running; you may want to create a separate command line that starts the emulator)
Now you should be able to just hit F5 (after the emulator is already running) to test your upgrade over and over.
(Ideally, if Visual Studio used MSBuild to do the Deployments to the emulator/phone, we could simply hook into that process and update the IS after deployment but before execution. Sadly, that is not the case)
I've tried to install "Oracle10g Release 2 ODAC (64-bit) 10.2.0.3 for Windows x64" from:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
on Windows 2008 server 64bit, but it crushes right after i run the setup.exe with the following error:
Problem signature: Problem Event
Name: APPCRASH Application
Name: javaw.exe Application
Version: 5.0.40.5 Application
Timestamp: 42a019e4 Fault Module
Name: StackHash_5c81 Fault Module
Version: 6.0.6001.18000 Fault Module
Timestamp: 4791adec Exception
Code: c0000374 Exception
Offset: 00000000000a6e97 OS
Version: 6.0.6001.2.1.0.272.7 Locale
ID: 1037 Additional Information
1: 5c81 Additional Information
2: fa1981fc0da3377cbbec45e762388188
Additional Information 3: 7698
Additional Information
4: 7defb6f15001721d919a359fb7888c17
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
can anyone direct me to a version that i can install the latesr version of ODP.NET for Windows 2008 server 64bit?
Best regards,
Guy Bertental
It's a really tricky. Before installing ODP.NET you need to already have working connection setup to oracle database. That means:
Step 1:
Oracle install client (never succeeded with that, not recommended) or Oracle client (succeeded on Win7 ultimate 64bit, file win64_11gR1_client.zip, installed with "Runtime" option selected). After client install make sure you can connect. From command line try "tnsping yourtnanamesentry" to check if tnsnames is ok, and after that "sqlplus username/pwd#yourtnsnamesentry" to check if you know valid user and password and really can connect. Memorize or write down oracle home name and path you choosed during install.
Step 2:
Install ODP.NET (I did with file ODAC1110720.zip). Use exactly the same oracle home name, but different path during installation.
Step 3: try connecting with visual studio. For "server name" I used this: "oraclexe:1521/xe". That means I have machine called "oraclexe" which has oracle listener on port 1521, and database with instance name "xe". It's so-called "EZCONNECT" name.
I'm not sure if Step 1 is really needed or not, because maybe step3 really uses just oracle instant client.
I know, it is real pain, but this works. It took me 2 days to connect to oracle, and I had to install almost 1GB of downloaded oracle software. They could and should make that much, much, much, much easier. Like one-click install that just works. This is shame how complicated client install is.
Donwload and install Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (32-bit) on your development computer.
Delete former references to Oracle.DataAccess on your project.
Add the new reference pointing to this new version.
In Visual Studio, after adding the reference select it, then choose properties to check the setting. Set “Specific Version” true , then check that “Copy Local” is false.
Build your solution using ANY CPU target.
Next, prepare your server. Install Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64) . When installing, select the RUNTIME OPTION.
Finally, deploy your solution to your server, as you always use to do. This time it should work.
The trick is to have the same ODAC version (11.2.0.1.0) on both the development and deployment enviroments. This ODAC contains the Oracle.DataAcces.Client which you should reference on your code to access classes like OracleConnection, OracleDataReader, etc.
I had problems because I had developed using ODAC 11.2.0.1.2 (32 bits, latest at this time) but there's no x64 version for this ODAC.
So, always use the latest stable ODAC version which has 32 bits and 64 bits version if you are going to develop on 32 bits and deploy on 64 bits.
Hi Ran into your problem, solution is get a copy of 10204_vista_w2k8_x64_production_client.zip (http://www.oracle.com/technetwork/database/10204-winx64-vista-win2k8-082253.html) run this & it will install the client.
Unpack ODAC10203x64.zip then go to All Programs->OracleHome->Oracle Installation Products & run the Universal Installer. When the installer runs at the Specify Source Location browse to the Stage directory created when you unpacked ODAC10203x64.zip then install as normal.
There is a ODAC112012.zip but this will not talk to Oracle 9 dB's so the above will resolve talking to legacy dB's.
Guy- have a look at this, it may help. Getting Oracle client working is a pain at the best of times, x64 must make it harder.
I had unexpected crashes in my application using Instant Client 10.2.0.3 on Windows Server 2008 x64. After reading a few posts about the lack of support for this platform, I upgraded the client to 11.1.0.7 and it works like a charm !
So I would be surprised if ODP .NET 10.2.0.3 would be stable on Windows Server 2008 x64, if you ever managed to install it. IMHO, your options are :
use another provider (Microsoft+client v11.1, or DataDirect...).
go with the 11.1.0.7 beta version if you dare...