I created WCF RIA services. It added app.config by default. But there is no option of Edit WCF Configuration that appears when you create simple WCF services. What am i missing? How do i get that GUI tool? Do i have to write all that xml and remember for the next time when i use it?
Thanks in advance :)
This is a known bug - at times, you have to select it from the Tools menu once and close it again right away, before it becomes available as a right-click context-menu option on your app.config file.
I would have hoped this would have been fixed in Visual Studio 2010 - but it's still there...
There should be a link in the main Tools menu to the editor, or alternatively run it externally and open your app.config from it's menu.
Open Visual Studio
Go to tools
Click on Edit WCF Service Configuration
Choose Tools --> Edit WCF Service Configuration Editor
1) Open Visual Studio command prompt & type SvcConfigEditor
OR
2)Navigate to C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\SvcConfigEditor.exe
In VS 2022, I could not locate a way to Edit Wcf configuration. Maybe I need to install more components of VS 2022 ? Anyways, I used Tools->External Tools menu item in VS 2022 to define a way to open the Wcf configuration myself.
Then hit start menu and search for 'cmd' or 'Developer command prompt' and choose the version suitable for you (e.g. 2022). Now enter :
svcconfigeditor
This opens a new window with svcconfigeditor and must succeed, or else you do not have installed Svc config editor anyways.. The tool which 'Edit wcf configuration' will open.
Next type this command :
where svcconfigeditor
This should show you the path to the executable on your system.
Locating svcconfigeditor executable on your Windows system
Go back again to Tools->Exernal Tools and hit 'Add' button
Give these values (example, last two values must be set):
Title: 'Edit Wcf configuration'
Command:
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\SvcConfigEditor.exe
Arguments:
$(ItemFileName)$(ItemExt)
Initial dir:
$(ItemDir)
External Tools - creating a edit wcf configuration tool window
Now - switch back to Solution explorer with the web.config file containing your web.config file.
Select the web.config file and choose :
Tools=>Edit Wcf configuration
Editing wcf configuration
Please note that I suspect Edit WCF configuration tools are better with older VS versions as WCF is getting replaced with
Related
unable to open Implemented solution into my system by using vs2013 and .net framework is 452, when i am trying to open solution First i get bellow dialogue box about TFS:-
Team Foundation Server version Control : The solution you are opening bound to source control on the following TeamFoundationServer http://tfs:8080/tfs/default connection. would you like to connect this server to try to enable source control integration? (yes/ no) , But i'm not using TFS here, then i clicked on No button then
Again I got one dialogue box with source control with in this dialogue box message like"The solution appears to be under source control, but its binding information cannot be found. Because it is not possible to recover this missing information automatically, the projects whose bindings are missing will be treated as not under source control." (Ok and help) i clicked on ok. then solution opened files with message load failed. ex:- In solution explorer projectName(load failed)
You can ignore the messages about the solution/project being under source control. That is not causing the project not to load.
You likely don't have some required Visual Studio plugin to open that project. The Output window should have more details as to why the project couldn't load. Typically this is because you don't have an older version of MVC installed.
Basically what I need is the following. Depending of if I publish to production server or developpement server I want to use different databases. I've read a little on the topic and found out that I'm supposed to have a web.debug.config and a web.release.config And depending on which I choose from the dropdownlist in Visual Studio 2010 the appropriate web.config is being used.
The problem Is that I only have a Debug mode and a single web.config
If I add a release via the Configuration manager and call it Production I can only copy the configuration from Debug and cannot edit it.
I was usign this MSDN tutorial set it up: Tutorial
and at step 3 i noticed I didn't have the option necessary to change the configuration
Creating and Modifying Project Configurations
To create a project configuration
Open the Configuration Manager dialog box.
Select a project in the Project column.
3. In the Configuration drop-down list for that project, choose New.
I don't have the new option I can only use the debug option
My project Is actually a Website
In VB
I FOUND IT:
Since I am using a webforms Web Site, this option is simply not available.
All,
I have a WCF Service I inherited from someone else.
When I make a Build either Debug or Release, the binaries go in the same folder.
I was under the impression that Visual Studio 2010 always has two folders, Debug and Release and depending on the type of the build the binaries go to the appropriate folder.
Any ideas?
Rgds,
MK
Look at the Build tab of the project's Properties. There you'll see the Output path, which might be set to the same folder for both Debug and Release Configuration (selectable through the drop-down on the top of the page).
Can someone point out any tutorials that help build windows services using msbuild.
Requirements :
- Should not use the csproj file
- Output should be the same as the publish option in Visual Studio
Updated question:
We have a project of type windows service in our solution. In this windows service, we are referencing a couple of libraries that reside on a different system (one of them is not strongly named). This solution also contains other class libraries and websites/web-apps.
I am trying to write a custom build that outputs a xcopy deployable version of the website, and a deployable version of the windows service. When I say windows service, it shows up on the Control Panel -> Services MMC.
The website build was easy via msbuild...however I am struggling with the windows service build. Until now, my fellow developers were using the right-click on the project file ,and click publish to publish the windows service. This generates a setup.exe file that helps the admins to deploy the service.
So, now here is my question:
I want to use msbuild to build my windows service.
I do not want to directly use the .csproj file in conjunction with msbuild to build the service.
The output my build file generates should match the output from the "publish" option (*the publish option generates a setup.exe file*)
In general, "the publish option" under the covers just runs a build with /t:Publish, i.e., it triggers a different target to the normal default 'Build' one.
Can you tell us more of what you are looking for, as opposed to not looking for?
Are you looking to generate an MSI? (If so, you definitely won't be using MSBuild if you're using the built-in .vdproj system - but be careful - this means having to put VS on a build server)
I want to distribute the installer package to my clients. Please anybody provide me details information about how can I make setup.exe file for my visual studio 2008 projects. If I am failed to provide any necessary info please let me know. Thanks in advance.
Though this is written for C#, the tutorial should work fine in VB.NET as well, if that's what you're using.
http://www.dreamincode.net/forums/showtopic58021.htm
In VS2008, add a new project. Then click "Other Project Types" and Setup and Deployment underneath that. You can then pick "Setup Wizard" this will guide you through creating a setup.exe and an MSI installer. This can then be built just like any other project, so when you make a change to your project, you can rebuild the setup.
In order to create an installer package, do the following:
Go to File -> Add New Project
Select Setup Project from "Setup and Deployment Projects"
From here you can add your files and when you compile it will generate an MSI file.
If you have access to a web server, i would publish your file using clickonce. This way anytime you make a change your users will automatically get the updates. To do so, right click the main project that you want to expose and click on the publish tab.