What do I need to install on a WP8 device that capable it to run my app writen by wp8 and SQL Server CE 3.5? - windows-phone-7

Please give me link of program that can capable phone wp8 run my application that written by Wp8 and VS.net 2013 and SQL Server CE 3.5.
Please give me link of software that I need to install on the phone.

SQL Server CE is not explicitly supported on Windows Phone. Silverlight-based apps can use LINQ-to-SQL though. See Local database for Windows Phone.

Finally i found reply for my question:
**Private file–based deployment (deploying the SQL Server Compact DLLs as part of the project)
***Users do not need administrative credentials to install the
application.
***SQL Server Compact will not be serviced by Microsoft Update.
Can also use
***ClickOnce deployment.
To deploy a SQL Server Compact 4.0 database by using private
file–based deployment
To open the Project Designer, in Solution Explorer/Database Explorer, double-click My Project if you are working on a Visual
Basic project (or Properties if you are working on a C# project).
Click the Publish tab.
Click Prerequisites and then clear the check box for SQL Server Compact.
Close the Project Designer.
Go to the directory that contains the SQL Server Compact DLLs. These are located in C:\Program Files\Microsoft SQL Server Compact
Edition\v4.0.
Select the seven SQL Server Compact DLLs and copy them:
Sqlceca40.dll
Sqlcecompact40.dll
Sqlceer40EN.dll
Sqlceme40.dll
Sqlceoledb40.dll
Sqlceqp40.dll
Sqlcese40.dll
Paste the DLLs into the project in Solution Explorer/Database Explorer.
Select all seven DLLs in Solution Explorer/Database Explorer and open the Properties window.
Set the Copy to Output Directory property to Copy if newer.
This will replace any earlier DLLs in an existing application with the newer ones if the application is updated.
Click the Show All Files button in Solution Explorer/Database Explorer.
Expand the References node.
Select System.Data.SqlServerCe.
Set the Copy Local property to True.
Because your development computer has the SqlServerCe DLLs in the global assembly cache, you must configure the application to use
the DLLs in the output directory.
Right-click the project in Solution Explorer/Database Explorer and select Publish to open the Publish Wizard.
Complete the wizard to publish the application.
The application is ready to be installed. Go to the location you
published to, and install the application to verify.

Related

How do I deploy an SSRS solution?

This is an extremely vague question because I don't know enough to know what I don't know. Here's my situation:
I have downloaded SSDT and connected to a data source (A SQL Server DB instance). I've created a report. I can preview the report in VS. I can publish the report from the VS build menu and it gets published to my local reports server that seems to have been installed by default at http://localhost/reports. I can use a browser to go to that url and see the report I created.
Now, the problem is that this is all only in my local development environment. I installed SSDT through Visual Studio and it auto-created my reports server. Is there a way to install a reports server without installing visual studio and publish the reports from a report solution using an MSI created by a packager like WiX? I'm having a hard time finding information about how to do this.
The report server is typically installed when you install SQL Server. If you want to publish reports so that others can use them do the following:
Go to your VS solution and right-click on the project then select properties.
Set the TargetReportFolder (this will be created if it does not
exist). This will usually reflect the name of the group of reports
you are working on (e.g. 'HR Reports')
Set the TargetServerURL to the report server on your SQL Server box for example http://mySQLServerBox/reportserver/
Set the TargetServerVersion to match your SQL Server installation version (SQL Server 2016 etc)
Now you can simply right-click a report rdl in VS and choose deploy, you can also do the same at the folder level to deploy all the reports in one go.
To access the reports, go to the web portal which will usually be http://MySQLServerBox/reports
I hope this is what you are looking for..

What's the minimum set of tools I need to open Windows Azure samples shipped by Microsoft?

I wanted to try open "Hello World" from here. I already had Visual Studio 2010 installed. I went here and downloaded WindowsAzureSDK-x86.exe and installed the SDK.
Yet when I double click the .sln in the sample Visual Studio opens the .csproj (the project with web role) just fine but complains it can't open the .ccproj file because its project type is not supported by this version of the application.
What else do I have to install so that I can open that .ccproj project file?
You need the Windows Azure SDK+tools. The easiest way to do this is to visit here and select "Get Tools and SDK." This will fire up the Web Platform Installer, which should do a much better job of setting up your environment.
A few more things: You'll need SQL Express (or SQL Server) installed as well. I "think" the Web Platform Installer will take care of that for you, but I'm not 100% sure. Also, you'll need to run Visual Studio as Administrator, to allow it to properly interact with the local Windows Azure simulator.
Turns out I needed to also install the thing called "VSCloudService.exe" on the same page. Once I installed it .ccproj files open just fine.

"Add SSIS Connection Manager" Dialog Doesn't Contain Custom Connection Manager

I am attempting to create a custom connection manager for performing SFTP operations from within SSIS. I have completed implementation, strong-named my assembly and installed it in both the GAC and the C:\Program Files\Microsoft SQL Server\90\DTS\Connections folder. The problem is that the "Add SSIS Connection Manager" dialog doesn't show my new connection type and I'm at a loss as to how to diagnose this issue. So far I have ensured that Everyone has Full Control to the C:\Program Files\Microsoft SQL Server\90\DTS\Connections folder.
Possibly related to this issue is that I cannot see the assembly when I browse the GAC, even though the gacutil program reports success when I run it to add the assembly.
What steps could I follow to diagnose the root cause of this issue? Is there anything else that I need to check to make it possible to add a add a custom connection manager?
EDIT: I should also note that the custom connection manager is compiled using .NET 4.0. This is why I cannot see the assembly in the GAC after installing it I believe, as the assembly is being placed in the %WINDIR%\Microsoft.NET\assembly folder rather than the %WINDIR%\assembly folder. I am using .NET 4.0 because of this issue.
EDIT #2: It turns out that if I create my custom connection manager in a Visual Studio 2008 project, compiled against .NET 3.5 then everything works fine. (Apparently using Visual Studio 2008 is a workaround for the version issue linked above.) So the real question now is why the SSIS Designer doesn't pick up .NET 4.0 custom tasks and connection managers.
Did you add it to the toolbox? The doco has this as a mandatory step.
Also, you must close and reopen SSIS Designer after you install a new or new version of a custom object.
You could also try resetting the toolbox.

Visual Studio Click Once deployment problem

I have a visual studio click once deployment. It's upgraded from VS 2008. The part that i'm having a problem with is the Prerequisites. I need for the .net 4 framework and Visual Basic PowerPacks 10.0 to be deployed with the app. I have the check box checked to "Create setup program to install prerequisite componets." I also have the Microsoft .net Framework 4 (x86 and x64) checked and the Microsoft Visual Basic PowerPacks 10.0 checked. the Download prerequisites from teh component vendor's web site is also selected. The publish says it's successful, but when i run the application, it tells me that i need the .net 4 framework installed and an ok button. click the ok button and i'm done. it doesn't provide a link, doesn't launch anything... nothing. From the googing i've done this is the way i'm suppose to have it setup. Can anyone give me some pointers as to what i'm doing wrong.
Thanks
shannon
It is better to add Prerequisites in the same published location. And select download Prerequisites from the same location option button in Prerequisites segment. When you publish build the application, All Prerequisites related folders will be created under the folder you have published the application. This will help you to copy and paste entire folder structure onto live server for deployment. This has to be done for the first time. For the later releases you only have to copy and paste application related files. Of course, If you change any of the Prerequisites then you have to copy them onto live server also.

VS 2008 Express - clickOnce question

I have the VS Express 2008 where there is only ClickOnce deployment option. I need my app to be simple ran by clicking on the exe file without any installation.
I have found out that after deleting both manifests and icon /which is always in the output directory even though its embedd with "Do not copy" option/ it works well. Is it ok or is there any cleaner way how to do that? I mean, if the app is not being installed but only ran, do I still need external manifest files? I tried to embedd them but these still persist external (tried "Embed manifest with default setting" option or add my own and selected from list).
EDIT: In the Express, there is only ClickOnce.
Thanks
If you want to run it from the exe, ClickOnce isn't quite right. ClickOnce executes as a .application, and you should be able to just click the radio button (on the "Publish" tab) for "The application is available online only", which avoids any local ClickOnce install.
Otherwise, just build as Release and take the /bin/Release output; this is your standalone exe app. To get the right trust, a .NET exe can be executed from:
local drives
mapped network drives (f: etc) with the right .NET service pack
anywhere if "caspol" has been used to set a policy
I believe in Visual Studio Express, ClickOnce deployment is your only choice.

Resources