How can I restore my SageMaker Studio Lab environment so that it connects successfully again to the d2l:Python kernel? I installed some packages using %pip (instead of %conda as I have since learned is recommended -- the packages I needed were not available on conda), and now my SageMaker Studio Lab will only connect to the Python kernel. Apparently, I have introduced some dependency issues with the packages I installed.
I have searched stackoverflow (and google) looking for a solution, but so far I have not found anything on point.
Related
So, I wanted to develop a little Filesystem Mini-Filter driver for windows.
I have installed Visual Studio 2019 and 2022 community edition with the following list of packages:
WDK
SDK
Python Development
Desktop development with C++
Universal Windows Platform development
Linux and embedded development with C++
Optional Packages:
C++ CMake tools for Linux
IntelliCode
Embedded and IoT tools
Legacy Embedded and IoT tools
With those installed I still don't have FileSystem Mini-Filter project type available. I also tried to search for it under Individual Components but it do not exist.
I came across this question: https://learn.microsoft.com/en-us/answers/questions/720582/filesystem-mini-filter-template-won39t-appear-in-v.html
Which seem to have worked for the guy, but a re-install did not work for me.
Is there anything I am missing here?
From Prerequisites on the setup property pages, I selected the option to Download prerequisites from the component vendor's web site
There is no Windows Installer 4.5 in the prerequisites to install option..
because every im installing my setup using the sqlexpr_x64_ENU.exe in custom actions to install, run the setup after the extracting sqlserver it pops up the window says
There is a problem with this Windows Installer package. Aprogram run as part of the setup did not finnish as expected. Contact your support personnel or package vendor
im using VS2017 on windows 10
Exclude MSI Engine: You should not include Windows Installer 4.5 with any package these days. This runtime is from back in the day of Windows Vista - we are long since on version 5. Windows Installer should be deployed only via Windows Update as of today - in my opinion. Leave the runtime out of your setup.
No Concurrency: You can not run an MSI setup from within another MSI setup via a custom action. This is due to technical restrictions. There is a mutex set when an MSI runs its actual installation sequence, and triggering another installation sequence from within it will fail. A similar answer on the topic.
Setup.exe Launcher: What you need is to install your pre-requisites via a setup.exe launcher instead. This runs installations in serial, not in parallel. Which version of SQL Server are you installing? I see only a couple of versions available in the Visual Studio Installer Project launcher.
Other tools have features to allow you to install a setup.exe with embedded packages of various kinds in sequence. I have explained a myriad of times how to do this in previous answers. Here are just a few that I found quickly:
SQL Server named instance with Visual Studio 2017 Installer project (basically exactly the same issue - I suggest WiX the open source, free alternative)
Custom installer for application in Visual Studio 2017 (I suggest WiX and several commercial tools that are easier to use - maybe try to read this one)
Cannot call command.exe(SQL Server Setup.exe) while calling C# CA with parameters
How to create a MSI file which simply copies a directory to Program Files? (tools list)
Combine exe and msi file in one installer
Visual Studio 2017 Installer Project - include VC++ 2015 Redistributable
The general situation:
The problem is not Windows Installer 4.5, it's the fact that you are trying to do a recursive MSI install (the SQL one from inside yours) which is not allowed and will fail.
The MSI 4.5 engine is pretty much obsolete, about 10 years old, and anyway it's not the issue, and it's not clear why you believe it is. But it IS in the Prerequisite list on my VS 2017 setup project prerequisites - see 3 - even though you almost certainly don't need it.
There are some SQL Express options available in the Prerequisites of the VS setup project - right click the project in solution explorer and choose Properties, then Prerequisites.
I have my my setup project in (Visual Studio 2015: Community Edition) ready to be built and create my program installer. But, obviously the program will not work on other computers without the appropriate redistributable package installed on the clients computer.
So, I need to set that up in my project but I do not know how. I read in a post on another site that it is located in:
Project>>Setup Properties>>Prerequisites
But, all I just see are selectables for ".net framework" related things. Also, I read that merge modules are not good to use due to servicing issues.
If you have any insight into whether I am needing to download an extension for the correct prerequisite to appear, use merge modules, or something else it will be greatly appreciated!
My WPF project requires Adobe Reader. Apparently when I try and run the installer, it says I need to have it installed before I run the installer for my project.
I was wondering how do I package it along with InstallShield so that the user can select the option to have Adobe Reader install before installing the main project instead of having to search for it online themselves to install it?
Is this even possible? I tried to search online but I'm having hard time finding results.
Right now I'm using InstallShield Limited Edition for Visual Studio 2012.
EDIT:
Here's one screenshot where I picked the settings:
EDIT #2: I found a redistributable .exe of Adobe Reader 9.1. Now, I am wondering how I can tie that into InstallShield?
I've spent some time with new Database project in VS 2008 and decided to go with it (really cool). But i've also discovered that i cannot build it on our CI-server where .NET SDK only is installed. I tried to put Microsoft.VisualStudio.TeamSystem.Data.Tasks.targets to the CI-server but it has too many dependencies on assemblies such as Microsoft.VisualStudio.TeamSystem.Data.dll.
Am i right that in order to build it i need VS 2008 Team System installed (unacceptable for CI-server) or there is a simpler solution?
You always need to install on your build server the same software you use to build on a developer machine. In this case, you do need the Data Edition installed. In the same way, if you had web tests as part of your automated test suite, you would need the Test Edition installed.