Although I came across this question but the link in accepted answer seems dead, and also this question is about VS 2008.
I am using VS2015, (and VB) and I have the same scenario. The configuration dropdown is still disabled. How do I set different application icon for different configurations?
Thanks
You can use pre-build step, or you can manually edit the project file in notepad to achieve the goal as mentioned here and also here.
Related
Goal - I am trying to change the visual studio solution explorer collapse settings, so that files with extensions such as .razor.css are collapsed under their 'parent' file so to speak.
Expected - My laptop environment does this automatically, I simply name the file (i.e. Index.razor Index.razor.css) and the situation resolves itself without any input from me.
Actual - My desktop environment does not do this, for some reason it lists all the files consecutively, only collapsing from the folders.
I have, no doubt, unchecked a box somewhere to get myself into this mess. I would rather not attempt to fix the problem with explicit entries in my .csproj or registry as recommended in this SO question, unless I absolutely must.
If anyone knows a way to control or edit this behaviour in Visual Studio Community 2022 then please do let me know!
The feature you're looking for is called File Nesting. It is customizable, but in web projects should also have smarter defaults for most of the file types shown.
For non-web projects, you may need to enable it manually. See this GitHub issue for details, but the TL;DR is to add this to your project file:
<ItemGroup>
<ProjectCapability Include="ConfigurableFileNesting" />
<ProjectCapability Include="ConfigurableFileNestingFeatureEnabled" />
</ItemGroup>
If you're in a web project or have applied the workaround, I'd first check that the feature hasn't been accidentally disabled. If it's enabled and still not working, consider filing a bug via the VS Feedback tool or via the GitHub repo mentioned above so the feature team can follow up with you directly.
So I right click on the solution > add > new project > find azure function > choose template > create that
And then nothing happens. If I swap to folder view, I see a new folder made for the function, but its an empty folder.
Weirdest thing is, this was working perfectly fine and a moment later, it became how it is right now. I've not updated vs in between, I've not restarted in between. It was literally closed vs, opened again, and then vs broke.
Older solutions that has functions in them, tried creating a new one, doesn't work same story. Made new solutions and start it off with creating a function, didn't work as well. Reinstalled vs, also did not help, still the same issue. Any ideas how I broke vs?
Also, this works from powershell, I can create functions from there and then go back to vs to add an existing project. However the functions I've build using this method had runtime errors (I think) when I publish them into azure. Regardless, I really would like to be able to create functions normally in vs.
As we can see from the comment section of the question, the solution was:
Go into Tools -> Get Tools and Features
download the .Net desktop development
As Maybemonday described in his/her comment, functions can be created afterwards.
You can solve the issues by installing the right tools.
When setting up the VS 2022 -OR- by navigating to Tools -> Get Tools and Features, install the following workloads:
.Net Desktop Development
Azure development
You can also observe the icon changes from a "Project" type to "Azure Function App" type.
I'm not sure why, but once I renamed C:\Program Files (x86)\dotnet to C:\Program Files (x86)\dotnet.delete, it started working. I think the x86 dotnet binary was earlier in the path and was causing issues.
Is there any way to find out whether or not a sharepoint solution which was previously deployed to a 2010 sharepoint site in release mode or debug mode?
thanks,
KS
There was a similiar question asked that can be found here. In short there is a utility called .Net Assembly Information that will give you the information you require. The utility can be downloaded from here.
You can use the excellent tool from Nirsoft which is GacView : http://www.nirsoft.net/dot_net_tools/gac_viewer.html if the dll is now stored in the gac and you don't have any more the initial package. It will allow you to peek into the global assembly cache and gather more information with other tools if needed since you can export the dll to your disk and analyze it peacefully with other tools like the one pointed by Matt.
I am using Visual Studio Ultimate. I have made a fairly long program which worked fine.
One day I find that the debug button was disabled and both the build and rebuild buttons do not work. I have tried opening the same project files in Visual Basic Express 2010 but still, the sane problem.
I don't really want to have to reinstall but I'm not even sure that that will fix the problem. Thanks in advance.
Is there a startup project? One project in the Solution Explorer should be in bold. Right-click the executable project and select "Set as StartUp Project". Additionally, open the Project Properties, Application tab, and ensure Application type is either "Windows Forms Applications" or "Console Application".
Did you try to reset the setting of your Visual Studio Ultimate?
Type: (In your visual studio command prompt)
devenv /resetsettings
Buttons disabled for just that program, or all programs?
I vaguely remember having a similar problem many years ago. Re-creating the project and solution files fixed it, I think (ie. create a new solution/project and import all the .vb files).
Another thing to check would be whether the compiled files have become read-only. Maybe VB.NET can't delete the old .EXEs
You need to build a test application. I think thats more difficult then making the application itself. In my personal opinion, your better off building the whole software in a notepad.
http://msdn.microsoft.com/en-us/library/ms182532.aspx
We've just newly decided to use NServiceBus on our project and we're experiencing some problems. Rather than "ask for a fish" every time we hit an issue, we'd prefer to "teach ourselves to fish". This means setting things up so we can step into the NServiceBus source code and understand NServiceBus more deeply.
We need some help figuring out how to pull this off. It is unclear how to get Visual Studio to successfully build NServiceBus upon each compile, since NServiceBus comes with its own Nant build process that uses ILMerge to create consolidated assemblies and so forth.
We have already tried building NServiceBus with the Nant script and then referencing those dlls and pdb's. However, that does not let us step everywhere, and it also does not let VS.NET and Resharper navigate via "Find Usages" and other features.
So what we would really like to create is a VS.NET Solution that builds our in-house software and NServiceBus, and allows us to seamlessly Step and Navigate between them.
Is this possible? What would we need to do to pull this off?
Not quite the exact answer you were looking for, but you can check out the post i made on debugging into NServiceBus which involves the following steps:
Downloading the source code.
Building the source code using the
"build.bat"
Then referencing the
dlls and pdb files in your
solutions, so that you can step into
the NServiceBus source code.
I've successfully change the logging behaviour to always to a Message.ToString() in our code so that the Log4Net logs were a bit clearer.
Check it out here:
http://www.craftyfella.com/2010/12/debugging-into-nservicebus-so-you-can.html
Hope it helps.
Dave