I need some help to determine why my VSTS build agent doesn't create an artifact in the drop folder
I have a solution that contains a website project (not a web application) and a logic project that i'm trying to build the website via VSTS. The build complete's correctly when i reference the solution as part of the "Process" step but nothing is added to the drop folder for the release process.
I have modified my build arguments to look for a publish profile that has been saved to the app_data/PublishProfiles (called vstsbuild) on the website project. The website doesn't have a project file but it does have a website.publishproj file at the root of the website.
Any idea why it won't publish an artifact would be helpful
VSTS Publish Logs
I've an application with a default theme (less files defined in app/sytles and included in app.less) and reachable at my main website (for example http://www.example.com)
Now I need to build the same application for different clients. Each client has its own style customization (client.less file) and its own assets (images, fonts, ...). This site will be deployed at, for example, http://client1.example.com.
My idea was to customize the build process passing an additional flag to the ember build --environment production command and customize the build process adding the client.less file when needed.
Something like ember build --environment production --theme client1 but as far as I can see there isn't the possibility to pass extra flags to build command.
Am I missing something? There is a better way to achieve that? Any help is really appreciate, I wouldn't maintain one project for each client.
In Resource folder I have a folder that contains many JS files. so while building the Application can I someway edit the build so that the only files which I need at that time should build rest of the files will be ignored. Is this possible in Titanium
The only way I found out that was applying resource filter on the project. But that is the manual task.
By applying the resource filter only the selected resources will get build and rest will be ignored..
No matter what I change in an asmx service in Visual Studio, the WSDL file stays always the same. Deleting methods, changing method signatures don't have any effect when I browse to service definition.
I have had a simular problem.
When removing an enum and replacing it by a string, the enum wouldn't go away from the wsdl. No matter what I tried (clean, rebuild, clear browser cache, other browser), it kept returning the enum as a complex type within the WSDL.
The solution in my case was remove the local folders of the project via windows explorer, then perform a get latest from TFS. After this the problem was solved.
Of course this solution only aplies when using a sourcecontrol system.
After changing your service, you must build it and ensure that the new version is running. One shortcut would be to build it (and make sure there are no errors), then right-click the .ASMX file and choose "View in Browser".
Also, although I'm sure you're aware of it, you should not be using ASMX web services for new development. Microsoft now considers ASMX to be a legacy technology. Use WCF instead.
I have encountered this problem and have a solution.
Cause: When you create a new "Web Service" project in Visual Studio, it automatically adds a "Service1.asmx" file to your project. You rename this file and change the class declaration inside of it, but Studio still thinks it's "Service1" wnd will only ever display the web service definition for "Service1".
Solution:
Delete all "bin" and "obj" folders in your project.
Copy the methods from your existing asmx file to notepad.
Remove the service from your project.
Add a new service to your project, with the name you want.
Paste the code from Notepad into the new service.
Rebuild All
Your asmx should now accurately reflect your web service and update normally on future builds.
I had today the very same issue. It was caused by a GACed version of the assembly that contained the type definitions exposed by the web service. I had to remove the assembly from the Global Assembly Cache first, like:
"C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\gacutil.exe" /u YourAssemblyNameWithouthDllExtebsion /f
Be sure to restart the web server hosting the web service to reload the new version of the assembly, for example, in case of IIS Express, you can kill the former process instance by PowerShell:
(Get-Process -Name iisexpress).Kill()
After that, the updated WSDL version was displayed as expected.
I am currently working on a SharePoint project that needs to use the Lists SharePoint web service (Lists.asmx). Therefore, we need to add a service reference to it in Visual Studio. However, we all develop and test on different virtual machines (with different VM names, URLs, etc.). The QA, Test and Production environments all have different names and URLs as well.
Adding a service reference adds a bunch of references to the URL that was specified when the reference was created (in the app.config. .wsdl, .disco, etc.). This is obviously a problem for us as code that works on one machine won't work anywhere else (which breaks the build and continuous integration) We also have to delete and add the service reference every time we work with code that was checked-in by someone else.
This must be a fairly common problem for people developing Web services so I wondered if there was a way around it. I know you can't really create a "dynamic" web reference, but perhaps the impacts of the URL change could be minimized somehow?
Thanks!
By default, the web-service uses the location where it was initially created. The WebService proxy has a URL property which can be set.
This example shows setting it dynamically: http://www.codeproject.com/KB/XML/wsdldynamicurl.aspx
EDIT:
You're also not limited to using the Add Web Reference feature in Visual Studio. You can use the wsdl.exe tool that ships with the .NET Framework SDK to generate the code file.