I have published my winforms client application with click once.
I am using visual studio 8 and OS Win Server 2003 SP2.
first using click once i was not able to use excel upload part of my app in windows 7 (64) but it was working on server 2003(32)/2008(64) and windows 8(32bit).
but after some googling I had some suggestions which i have changed.
List of changes I have done
changed the OLEDB connection string to Provider=Microsoft.ACE.OLEDB.12.0;Data Source='".
changed the target platform to X86.
removed all the office components from the server and re-installed AccessDatabaseEngine.exe.
Checked the MIME type all the .deploy manifest and all are
there(also checked the office extensions).
After doing these changes I was able to use the Excel upload on all the OS.
But after 3 versions now its again stopped working.
Now I am out of clues what went wrong.
Related
I was trying to use Team Foundation Server 2012 with Sql Server Management Studio 2012. I installed the Microsoft Visual Studio Team Foundation Server 2013 & 2015 MSSCCI Provider 32-bit and choose it as Current source control plug-in under tools -> Source Control -> Plug-in Selection of SSMS.
The problem is when I create/open a solution, for the very first time, and try to add a solution to source control from file -> source control -> Add Solution to Source Control a dialog box appears asking to connect to tfs once connected and location of server is specified on server and ok button is pressed it shows a warning that my workspace is a local workspace and local workspaces do not work properly in MSSCCI. It asks if I want to change it to server workspace once I click on Yes
I get the following error
Unexpected error encountered. It is recommended that you restart the application as soon as possible.
Error: No such interface supported
File: Vsee\internal\inc\vscomptr.inl
Line number: 259
Trying again yield this error message as soon as I choose Add Solution to Source Control.
I have tried some of the hotfixes provided by Microsoft from the link :
https://support.microsoft.com/en-us/kb/2727824 but they do not install on my machine saying that my SSMS version is newer.
How can I get this problem resolved ?
As described in this article - Team Foundation Server 2012 brought up a change in the workspace options bringing a new type of workspace – a local workspace. A local workspace is an improvement in offline work and it allows performing a number of source control operations without the connection to Team Foundation Server.
For more information about server workspaces vs. local workspaces refer to the following article: http://blogs.msdn.com/b/phkelley/archive/2013/05/29/server-workspaces-vs-local-workspaces.aspx
The article states that Microsoft continues to fully support the older kind of workspaces (from VS/TFS 2005 - 2010), but they now call these “server” workspaces. In the VS/TFS 2005 - 2010 documentation there is no mention of these workspaces ever being called “server workspaces” – because before the existence of local workspaces, there was no need to have a special name for them - they were just “workspaces.”
Hope I helped.
I am using TFS Online (Visual Studio Online), SQL Server Management Studio 2012, Windows Server 2008 R2, and installed Microsoft Visual Studio Team Foundation Server 2013&2015 MSSCCI Provider 32 bit. I can add new solution in SSMS and add to source control with no issue. You might want to
1. go back and create the server workspace FIRST in Team Explorer 2012.
2. Then re-create the solution (Make sure you check the Add to Source Control),
3. then select the TFS with the correct server workspace.
4. from Solution Explorer, right click on the project and add existing items.
Hope it helps
I have this bizarre scenario happened to me today morning. I was scheduled to publish a new version of my application and I did it successfully (as Visual Studio 2012 output said!). The Publish HTML also had the correct version in it.
Note
- Development Terminal runs on Windows 7 SP1 with Visual Studio 2012 Update 4,
Crystal Reports 13 for Visual Studio and Kaspersky EndPoint Security 10 for Windows;
- Files are copied over a FTP to a Windows Server 2003 server within the LAN;
- User Terminals are loaded with Windows 7 SP1 and Windows XP SP3 with Kaspersky EndPoint Security 10 for Windows;
When I checked with Users, some said new release weren't applied in their terminals. Further investigation revealed that those whom had Windows XP, had itself updated with the latest release, where as those whom had Windows 7 did not detect any updates available and runs the previous released version when ran without any errors.
Further, I noted that in Users who were having Windows 7, if the Application is Run from Start-up menu it loads the previous release which had been there earlier. I tried uninstalling and deleted all contents in
C:\Users\\AppData\Local\Apps\2.0*
and launched the application from Publish.html web page again. Then I noticed that it prompts for installation and when I clicked "OK" it only installs an application with 6.95MB where as the new application is 7MB+. This proves that ClickOnce picks the previous release from some where, which I cant figure the location. I even tried up increasing the Publish Version thinking it will detect a signature change but did not. :(
I have checked the Manifest file in the server, it had the latest version specifying in it.
Let me know of any location where I could further investigate; I mean where does ClickOnce stores all files other than C:\Users\\AppData\Local\Apps\2.0* and where I could find the Log file which ClickOnce creates which I'm struggling to find
I have published releases earlier, but this is the first time I'm getting such problems. Since my last release which I publish, I had only installed Update 4 for Visual Studio.
Did anyone come across it?
These were my Settings:
Everything worked today morning. It seems, some client level cache was a reason to this problem in Windows 7 users.
Should I have urged the users to re-start their machine, this would have not caused; I presume. But nevertheless happy that everything went on board with the new update.
I have a Windows Forms application that I am using ClickOnce deployment for and everything publishes fine when I am attempting to publish in Windows XP. When I try the same publish feature in Windows 7, it hangs on the publish step.
I am using a UNC path (file share) to the server (Windows Server 2008 R2 with IIS 7). Why might this happen?
I never receive an error message and the process cannot be cancelled. I have to force-close Visual Studio and restart my Windows 7 PC because Visual Studio has some of the files locked.
UPDATE:
I was able to set full-control permission on the folder on the destination server for my domain PC, and I was then able to publish once. Then, every subsequent deploy hanged. I did notice however that it always hangs when it's trying to copy the Office Interop files. Why would this be?
UPDATE (2):
This is definitely related to the Office 2010 PIA files. Why would it not publish them? Again, this works flawlessly on Windows XP, but when I perform the deployment on Windows 7, the PIAs are not published.
It could be a UAC issue. Try running Visual Studio as an administrator when you do a publish.
I was developing an Application that requires a database to store and retrieve data. I am developing the applcation on Visual Basic 2010 Express Edition and using SQL Server Compact Edition for database, on a Windows 7 PC. The Application works perfectly on Windows 7 on my PC. The problem arises on the system of my client who is using Windows XP.
I asked him to install .NET Framework 4.0 and SQL Server CE and send him a copy of the build Application. But when he executed the application and reached a form where database was being used, he encountered and error saying "Access to the database file is not allowed. [ File name = D:\prototype\app\master.sdf ]" and on clicking on continue the form loads but data from the database is not loaded, since it's not connected.
The same problem occurs on windows 7 if i copy the app folder to Program Files directory on Windows 7. But It doesnt occur if i execute the application as "Run as Administrator"
So I require your help to figure out what might be going on and why can't the application access the database simply as it is working on windows 7 (except in the program files directory).
Thanks in advance,
Best Regards
"The user need read-write access to the database file, so you must put it in an suitable location, and change your connection string accordingly."
http://erikej.blogspot.dk/2011/02/using-sql-server-compact-40-with.html
By EricEJ
All,
I am using the VS2010 database connection dialog that Microsoft have released (download from here). I am using this without any problems on Windows 7. However, when I install the application on Windows XP (using the 'Publish' option in VS2010) I get the following error
Using NSIS, the application installs but upon trying to launch the VS2010 dialog I get the following error
Clearly the first error is telling me what the problem is, but as I have never come across this before I am not sure what I can do to address/fix it. Could this be associated with not using the manifest correctly?
As always any help is most appreciated.
Seems that in your Windows XP is missing the library for Microsoft SQL Server Compact 3.5
You could download the bits from here